feat: support multiple versions of the pgroonga extension

[jfroche]

Build multiple versions of the pgroonga extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17

also includes

Fix Groonga/PGroonga Installation in Dockerfiles

Summary

aligns the groonga/pgroonga installation approach in Dockerfiles with the Ansible deployment method, ensuring consistent behavior across different deployment strategies.

Problem

There was an inconsistency in how groonga and pgroonga packages were being installed between Ansible-based deployments and Docker-based deployments:

Ansible Approach (Correct)

• Installed supabase-groonga as a separate Nix package
• Explicitly set the GRN_PLUGINS_DIR environment variable pointing to /var/lib/postgresql/.nix-profile/lib/groonga/plugins
• This modular approach ensured groonga plugins were properly located

Dockerfile Approach (Incorrect)

• Relied on groonga/pgroonga being bundled within the main postgres Nix package
• Did not set the GRN_PLUGINS_DIR environment variable
• This could lead to runtime issues where pgroonga extension cannot locate groonga plugins

Changes

Files Modified

• Dockerfile-15
• Dockerfile-17
• Dockerfile-orioledb-17

What Was Changed

For each Dockerfile:

1. Added dedicated groonga build stage (after the walg stage):

   ####################
   # setup-groonga
   ####################
   FROM base as groonga
   
   WORKDIR /nixpg
   
   RUN nix profile install .#supabase-groonga && \
       mkdir -p /tmp/groonga-plugins && \
       cp -r /nix/var/nix/profiles/default/lib/groonga/plugins /tmp/groonga-plugins/
   
   RUN nix store gc
   
   WORKDIR /

2. Copy groonga plugins to production image:

   COPY --from=groonga /tmp/groonga-plugins/plugins /usr/lib/groonga/plugins

3. Set GRN_PLUGINS_DIR environment variable:

   ENV GRN_PLUGINS_DIR=/usr/lib/groonga/plugins

This fix ensures that the pgroonga extension (configured in ansible/files/postgresql_config/supautils.conf.j2) will work correctly in Docker-based deployments, matching the behavior of Ansible-based deployments.

[hunleyd]

rebase to fix conflicts?

Thanks for your review. rebase was a success. dismissing only to unblock, and approving to merge