Feat: Standalone Storage Service

[fenos]

What kind of change does this PR introduce?

Standalone Storage Service

Base migrations are now part of the service.
Storage can now be run as a fully standalone service.

Fully decoupled from auth,realtime,postgrest

Notable changes

Migrations

Added a new migration 0002-storage-schema.sql

To keep backward compatibility and not break self-hosted instances the migration tool is now able to "refresh" the migrations table if it detects that the newly created migration is not present in the migrations records.

This refreshing mechanism only takes place for projects that have already run the migrations at least once.

New installations and new projects will start fresh and don't need to refresh

Granular Roles

Introduced 4 new environment variables for new installations

• DB_ANON_ROLE default anon
• DB_SERVICE_ROLE default service_role
• DB_AUTHENTICATED_ROLE default authenticated
• DB_INSTALL_ROLES default true
• DB_SUPER_USER default supabase_storage_admin
• DB_SEARCH_PATH default ''

If these roles are already present in the database we can simply pass DB_INSTALL_ROLES=false and the migration will not install these roles

[inian]

I still see base migrations has a dependency on a extensions schema and supabase_admin. Do we really need supabase_admin role here? Shouldn't supabase_storage_admin role be sufficient?
Do we need realtime publication here?

Any other schema, extension or role thats not required for the standalone functioning of storage?

[coveralls]

Pull Request Test Coverage Report for Build 7450741493

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.5%) to 84.248%

---

Totals
Change from base Build 7446101654:	-0.5%
Covered Lines:	7851
Relevant Lines:	9245

---

💛 - Coveralls

[github-actions]

🎉 This PR is included in version 0.44.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀