Relocate `postgis` extension from public to extensions schema

Hoping someone can run the documented PostGIS relocation script.

Project: wduolvnnnnfsnuyghenp (Free plan, org conwad-lab) PostGIS: 3.3.7

Advisor flags rls_disabled_in_public (ERROR) on public.spatial_ref_sys + extension_in_public (WARN) on postgis. Prepping for a DORA audit — both clear by relocating postgis from public → extensions.

Per https://supabase.com/docs/guides/database/extensions/postgis (Troubleshooting), the sanctioned fix on PostGIS ≥ 2.3 is the six-statement transaction your team runs server-side:

BEGIN;
  UPDATE pg_extension SET extrelocatable = true  WHERE extname = 'postgis';
  ALTER EXTENSION postgis SET SCHEMA extensions;
  ALTER EXTENSION postgis UPDATE TO '3.3.7next';
  ALTER EXTENSION postgis UPDATE;
  UPDATE pg_extension SET extrelocatable = false WHERE extname = 'postgis';
COMMIT;

Pre-flight done (idempotent):

ALTER ROLE anon          SET search_path = "$user", public, extensions;
ALTER ROLE authenticated SET search_path = "$user", public, extensions;
ALTER ROLE service_role  SET search_path = "$user", public, extensions;
ALTER ROLE authenticator SET search_path = "$user", public, extensions;

So ST_* calls resolve from public now, from extensions after the move — zero code rewrite, zero downtime expected.

Surface at stake: 4 tables with geography(Point,4326) (~1,023 rows), 3 RPCs using ST_DWithin/ST_Distance for a 3km geofence, MCP hotel-pairing. Rather absorb a delay than a disruption — if anything makes this risky please pause and ping me first.

No dependent PostGIS extensions installed (only postgis core active).

No priority expected — Free plan is community-only. Thanks 🙏