Security Advisor flags spatial_ref_sys with "RLS Disabled" but users cannot enable RLS on it

# Security Advisor flags `spatial_ref_sys` with "RLS Disabled" but users cannot enable RLS on it ## Bug report - [x] I confirm this is a bug with Supabase, not with my own application. - [ ] I confirm I have searched the Docs, GitHub Discussions, and Discord. ## Describe the bug The Security Advisor flags `public.spatial_ref_sys` as "RLS Disabled in Public" (Critical). However, this table is created by the PostGIS extension and owned by `supabase_admin`. Users cannot enable RLS on it because they are not the table owner: ``` ERROR: 42501: must be owner of table spatial_ref_sys ``` This creates an unresolvable critical warning in the dashboard. ## To Reproduce 1. Create a Supabase project 2. Enable the PostGIS extension 3. Go to Security Advisor in the dashboard 4. See critical warning: "Table public.spatial_ref_sys is public, but RLS has not been enabled" 5. Attempt to run `ALTER TABLE public.spatial_ref_sys ENABLE ROW LEVEL SECURITY;` in the SQL Editor 6. Get error: `must be owner of table spatial_ref_sys` ## Expected behavior Either: - The Security Advisor should exclude known extension-managed tables (`spatial_ref_sys`, `geometry_columns`, etc.) from RLS checks, or - Supabase should automatically enable RLS with a public read policy on these tables during extension setup ## System information - OS: Windows - Browser: Chrome - Dashboard (not supabase-js specific) ## Additional context The `spatial_ref_sys` table contains only public coordinate reference system definitions (EPSG codes). It has no user data and poses no security risk without RLS. The warning is a false positive that cannot be actioned by the user.