[SNOW-198] Create ownership database roles for data warehouse

[philerooski]

synapse_data_warehouse/database_roles/V2.31.0__database_access_roles.sql

• Since these are database-level objects, as opposed to account-level, we create these database roles and make grants on them within a versioned script.
• This is the first time we are creating a database-level object which is not a schema. Normally, a versioned script would exist within its associated schema folder, like synapse_data_warehouse/synapse/.... But since database roles are database-level objects, I write them to their own folder under synapse_data_warehouse/database_roles. I would like to move synapse_data_warehouse/synapse and synapse_data_warehouse/synapse_raw to synapse_data_warehouse/schemas/... for uniformity, but I'll need to check if this works well with the synapse_data_warehouse/schemachange-config.yml file. Let me know if you prefer the database_roles folder alongside of the schema folders like it currently is in the PR.

admin/grants.sql

• Although SYSADMIN has OWNERSHIP privileges on most or all of the objects having their ownership transferred here, we need MANAGE GRANTS privileges to COPY CURRENT GRANTS along with ownership.
• Granting ownership can be finicky, and running these grant commands every time we deploy to production might cause some issues. I'll do some additional testing to make sure these grants are idempotent.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[philerooski]

I use CREATE OR REPLACE instead of CREATE IF NOT EXISTS because if we were to rollback/replay these changes, we would want our database roles to be privilege-free.