Destination Snowflake: support oauth

[igrankova]

Tell us about the problem you're trying to solve

With the release of Airbyte Cloud, we need to start supporting Oauth for this connector, since it's the recommended way of authenticating users into a SaaS application.

If this connector doesn't support oauth already (i.e: doesn't accept a client_id and client_secret) then we need to update its spec to accept those parameters. There are two ways to do this:

If the connector already supports some auth mechanism like api_key, I suggest that this be a oneof nested inside a top-level field called "authentication":

{ authentication: { type: object oneOf: [ // api key, // oauth ] } }

If the connector only supports webflow oauth, then no changes are needed to the properties format and we will only need to add annotations.

See the connector spec reference in the docs for reference on how a oneof can be implemented.

This should be done in a backwards compatible manner i.e: users currently supplying authentication info in the config's top-level should not be impacted by this change.

Acceptance criteria

The connector supports oauth webflow authentication with client_id/client_secret in a backwards compatible manner
Oauth properties are annotated properly.

[igrankova]

Created the Public Snowflake SECURITY INTEGRATION, name: AIRBYTE.
To receive Client ID and Secret:
In the Snowflake App add a new worksheet and run the sql query: select system$show_oauth_client_secrets('AIRBYTE');
LastPass cred name: Snowflake integration test account
Reference document: https://docs.snowflake.com/en/user-guide/oauth-intro.html#snowflake-oauth-authorization-flow

[etsybaev]

https://community.snowflake.com/s/article/HOW-TO-OAUTH-TOKEN-GENERATION-USING-SNOWFLAKE-CUSTOM-OAUTH

[etsybaev]

#11093

[etsybaev]

https://github.com/airbytehq/oncall/issues/185