feat: keep pgjwt present but deactivated for orioledb only to avoid r…

[samrose]

This PR will also need to address this change in https://github.com/supabase/infrastructure/blob/develop/init-scripts/project/00-initial-schema.sql#L20 as well.

At this time, the scope of this change is to fix the following issues only. If we need to expand the scope, it needs to be in a different PR.

1. Remove pgjwt from the dbExtensions17 filter in flake.nix to ensure it's not included in PostgreSQL 17 builds
2. Keep pgjwt in orioleFilteredExtensions so it's included in the orioledb-17 package
3. Keep pgjwt in the supautils.privileged_extensions list in supautils.conf.j2 since it's a privileged extension
4. Ensure pgjwt is not in the shared_preload_libraries list in postgresql.conf.j2 to prevent it from being loaded by default
5. Keep the existing sed commands in Dockerfile-orioledb-17 and ansible/tasks/stage2-setup-postgres.yml that remove pgjwt from supautils.conf

This setup will:

• Include pgjwt in the orioledb-17 package
• Make it available as a privileged extension
• Not load it by default in the AMI or local testing in orioledb-17
• Retain it's deprecation in pg 17.4
• still enabled in pg 15.x

So the only change needed was to allow pgjwt to be built and delivered with oriole-17 package + adjusmtment of init and test sql.

[samrose]

...testing in progress

[samrose]

Pause/restore test from 17.0.1.053-orioledb to this version 17.0.1.067-orioledb-pgjwt-2 worked