Studio: storage policies covering multiple buckets are only listed under the first bucket; negated policies are misattributed and can be wrongly deleted with the wrong bucket

# Bug report - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). ## Describe the bug `extractBucketNameFromDefinition` in `apps/studio/components/interfaces/Storage/Storage.utils.ts` parses a policy definition by splitting on `' AND '`, taking the first segment containing `bucket_id`, and returning the text between the first pair of single quotes. It can only ever return one bucket, and it does not distinguish `=` from `<>`. Three surfaces consume it and all inherit the problem: 1. The Storage Policies page. A policy like `bucket_id IN ('avatars', 'logos')` (stored by Postgres as `bucket_id = ANY (ARRAY['avatars'::text, 'logos'::text])`) is listed under `avatars` only, and is invisible under `logos`. A negated policy like `bucket_id <> 'avatars'` is listed under `avatars`, the one bucket it does not apply to. 2. `useBucketPolicyCount`, which shows per bucket policy counts, undercounts for the same reason. 3. `DeleteBucketModal`, which deletes the policies "tied to" a deleted bucket using this parser. Deleting the `avatars` bucket deletes a `bucket_id <> 'avatars'` policy, which is a policy protecting every bucket except avatars. Whether a multi bucket policy is deleted depends on which bucket happens to appear first in the definition. Since this page is where users audit which access rules protect each bucket, wrong grouping can give a false picture of storage security, and the delete path can silently remove policies that still guard other buckets. ## To Reproduce 1. Create two buckets, `avatars` and `logos`. 2. In the SQL editor, run: ```sql create policy "Multi bucket read" on storage.objects for select to authenticated using (bucket_id in ('avatars', 'logos')); ``` 3. Go to Storage, then Policies. The policy appears under `avatars` only; und…