Issue due to removal of region from Snowflake URI

[tatiana]

Version: astro==0.4.0

Context
The way we are building Snowflake URIs seems to be prone to errors.

Recently, a user had reported that Snowflake had deprecated the usage of the region in the host URI, and we made this change:
541038c#diff-4498bebc277444fc4d9662514a3a2e2eacdcdfd139e160abd6fdb16b0e43a854L31

Although the user was happy with the change, other users who were being able to successfully use Astro started experiencing the error:

snowflake.connector.errors.ForbiddenError: 250001 (08001): None: Failed to connect to DB. Verify the account name is correct: GP123.snowflakecomputing.com:443. 000403: 403: HTTP 403: Forbidden

The goal of this ticket is to resolve the issue so both users are able to use Astro, if possible removing any complexity within Astro.

Additional details

Based on the Snowflake documentation:

For example, if your account locator is xy12345:

    If the account is located in the AWS US West (Oregon) region, no additional segments are required and the URL would be xy12345.snowflakecomputing.com.

    If the account is located in the AWS US East (Ohio) region, additional segments are required and the URL would be xy12345.us-east-2.aws.snowflakecomputing.com.

One approach we can consider taking is to remove altogether the need for the TempSnowflakeHook class and trust the user to set the Snowflake host which works for them.

[tatiana]

This was solved as part of #95