Document warehouse provisioning at user role level

* General data --> Lumos adds the Snowflake `snowflake_analyst` role to their account.

* SAFE data (you must be or will become a designated insider) --> Lumos adds the Snowflake `snowflake_analyst_safe` to their account. See the [SAFE Guide](/handbook/enterprise-data/platform/safe-data/#snowflake) for the needed approvals.

All users will have access to `dev_xs` and `reporting` -(size M) warehouse. When creating the user, the `dev_xs` warehouse as default warehouse.

All users will have standard access to `dev_xs` warehouse. Warehouses are provisioned at the user role level, which enables finer-grained warehouse assignment. This approach allows to optimize resource allocation and cost management by assigning appropriate warehouse sizes to GitLab Team Members. Larger size warehouses could be requested via regular Access Request proces. 

Snowflake can be used to perform analyses on the data that is available by writing SQL-code. Anything created and any outcome of the analyses is considered as an [ad-hoc analyses](/handbook/enterprise-data/how-we-work/data-development/#data-development-at-gitlab). It is important to know that anything that is created (i.e. worksheets and dashboards) is not version controlled and not supported or managed by the Central Data Team. I.e. When a team member off-boards from GitLab, the worksheets and dashboards are not accessible anymore. In order to persist analyses, team members can build Tableau workbooks, store code snippets in a GitLab project, or commit code to the Data Team's [dbt project](https://gitlab.com/gitlab-data/analytics/-/tree/master/transform/snowflake-dbt).