several tightly coupled / hardcoded thigns in postgresql migration sqls

[STRRL]

Hi! Supabase Teams!

We are a small startup and using supabase for our business. For the connectivity reasons, we're considering self-host several supabse components(like gotrue, storage, etc.) for our china mainland business.

When we're trying to bootstrap the supabase/storage, we found that there are 3 things which is hard to tuning:

• there is a hard-coded postgres role in migration SQL https://github.com/supabase/storage/blob/21e9bdec7e25e146c0b00c67159cb4116976f0d7/migrations/tenant/0002-storage-schema.sql#L29
• it would change this role's default search path as storage https://github.com/supabase/storage/blob/21e9bdec7e25e146c0b00c67159cb4116976f0d7/migrations/tenant/0002-storage-schema.sql#L165
• it's hard to configure just ignore self-singed certificates during connect the database

If you also think that would be problems for user, and give us some suggestion on how to fix them, we're glad to make some contributions on that. Thanks!