Want to use Supabase Storage with other Auth (custom JWT)

Right now I'm using clerk.dev's Auth solution (per Supabase's instructions: However, it's currently not possible to use Supabase Storage with these users, because the storage.objects table defines owner as a uuid FK field to the auth.users table's id. The Supabase+Clerk integration, meanwhile, uses a JWT generated by Clerk as the bearer token, which has a sub value that is not a uuid nor is it in the auth.users table.

It would be great if we could edit the storage.objects schema so that we could loosen the definition of the owner column and define our own RLS restrictions there. As-is, I'm going to have to split my app's storage out to a solution like S3, when I had been hoping to get everything done within Supabase.