feat: adding secure views for snowflake

[benfdking]

Related to #3070

NOTE I know I need to revert a number of unnecessary format changes.

A few thoughts:

• I don't think this is tested enough because I haven't run anything against Snowflake
• I am not certain about the way I create the views, it's a bit ugly
• More generally, I am slightly nervous about the approach of just adding properties to the root model configuration that are specific to individual engines, as it feels like a way to get way too many confusing configuration points

[tobymao]

@benfdking is it possible to make this more generic? we've also had a request for transient tabels, i wonder if we can make it easy to specify any type of create table kind

[benfdking]

I believe this approach is more versatile and can be applied to both TABLE and VIEW types. However, there is a conflict between the new creatable_properties and materialize properties in the case of Snowflake view. This is because, the properties control the same part of the query and according to the Snowflake documentation, the SECURE property has to come first.

The issue can be easily resolved by checking the properties and moving SECURE to the beginning if it is present but I was wondering if we should use this as an opportunity to remove the materialize property?

[tobymao]

@benfdking what would removing it entail?