Cast database errors to click exceptions for UX

[sfc-gh-turbaszek]

Pre-review checklist

• I've confirmed that instructions included in README.md are still correct after my changes in the codebase.
• I've added or updated automated unit tests to verify correctness of my new code.
• I've added or updated integration tests to verify correctness of my new code.
• I've confirmed that my changes are working by executing CLI's commands manually on MacOS.
• I've confirmed that my changes are working by executing CLI's commands manually on Windows.
• I've confirmed that my changes are up-to-date with the target branch.
• I've described my changes in the release notes.
• I've described my changes in the section below.

Changes description

Cast DatabaseError to ClickException. Before:

➜ snow sql -q "select foo"
select foo

An unexpected exception occurred. Use --debug option to see the traceback. Exception message:

000904 (42000): SQL compilation error: error line 1 at position 7
invalid identifier 'FOO'

and after

➜ snow sql -q "select foo"
select foo
╭─ Error ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ 000904 (42000): SQL compilation error: error line 1 at position 7                                                                                                                                            │
│ invalid identifier 'FOO'                                                                                                                                                                                     │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

[sfc-gh-bdufour]

Telemetry will then report this as a non-CLI error too, right?

Any thoughts on whether we should do something similar for ProgrammingError coming out of the connector?

[sfc-gh-turbaszek]

Telemetry will then report this as a non-CLI error too, right?

That's correct, reporting happens before type casting. I think it's ok. We don't distinguish between expected and unexpected db errors.

ProgrammingError is a DatabaseError so it's already covered.