feat(source create snowflake): Support format --account {org}.{account}

[spencerwilson]

• Upgrade regress dep
• Support more user-friendly --account {org}.{account} format when creating Snowflake sources

Test plan

Failure:

% cargo run -- source create snowflake -n testing-easier-identifier --account ASDF --user redacted --password redacted --database redacted
error creating source: Invalid account identifers given. Provide account identifiers either via `--account ${ORG_NAME}.${ACCOUNT_NAME}, or via `--organization ${ORG_NAME} --account ${ACCOUNT_NAME}`.

Success:

% cargo run -- source create snowflake -n testing-easier-identifier --account ABC123.DEF456 --user redacted --password redacted --database redacted
Source created

&& verifying the expected values were persisted:

dpm=> select source_parameters->'organization', source_parameters->'account' from source where name = 'testing-easier-identifier';
 ?column?  | ?column?
-----------+-----------
 "ABC123" | "DEF456"
(1 row)

[spencerwilson]

Current dependencies on/for this PR:

• main
  • PR feat(source create snowflake): Support format --account {org}.{account} #206 👈

This stack of pull requests is managed by Graphite.

[spencerwilson]

This was motivated by 0.6.0 wrongly rejecting a valid pattern:

^(?<org_name>[a-zA-Z][a-zA-Z0-9]*)[.-](?<account_name>[a-zA-Z_]+)$
thread 'main' panicked at src/command/snowflake.rs:34:6:
called `Result::unwrap()` on an `Err` value: Error { text: "Invalid token at named capture group identifier" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[spencerwilson]

Going forward, I'd like to accompany any non-trivial .unwrap() calls with // SAFETY comments, explaining why they won't panic. The hope is that this practice will promote quality and make it easier to audit the codebase for any preexisting, unjustified unwrapping.

[ajmasci]

TIL: Safety comments.