Snowddl

- Expose internal query builder `SnowDDLQueryBuilder` as public class. Now it can be used in external projects.
- Minor internal changes in SQL formatter.

- Implemented proper ALTER for `FILE_FORMAT`, fixed a bug when SnowDDL tried to re-create `FILE_FORMAT` which already exists. Also, `EXTERNAL_TABLE` will not lose association with `FILE_FORMAT` after ALTER.
- Object types `EXTERNAL_FUNCTION`, `EXTERNAL_TABLE`, `FUNCTION`, `PROCEDURE` are now correctly resolved as REPLACE instead of ALTER, when object was actually replaced by `CREATE OR REPLACE ...` command.

- Fixed incorrect encoding while opening files on Windows machines. Now it is explicitly set to `utf-8`.

- (!breaking change!) Parameter `after` of `TASK` object type is now array of strings to support newly released [DAG-feature](https://docs.snowflake.com/en/user-guide/tasks-intro.html#dag-of-tasks). Previously it was a basic string.
- Fixed a major bug with dependency resolution, when allocated full names were not preserved between cycles properly.
- Allowed `$` (dollar sign) character in identifiers.
- Added basic `expression` parameter to `TABLE` columns, as an experimental feature. Currently, it requires fully resolved and normalized SQL expression. Otherwise, SnowDDL will fail to perform expression comparison and suggest re-creating a table on every run.
- Added `--include-databases` and `--ignore-ownership` options for `snowddl-convert` entry-point.

- Implemented `OUTBOUND_SHARE` object type.
- Implemented test version of `INBOUND_SHARE` object type, which is currently disabled during normal execution.
- It is now possible to specify `grants` for `TECH_ROLE` and `OUTBOUND_SHARE` using [Unix-style wildcards](https://docs.python.org/3/library/fnmatch.html).
- Fixed typo in `EXTERNAL_FUNCTION` blueprint parameter `api_integration`.
- Fixed type in `TECH_ROLE` JSON-schema used to validate YAML config.
- Improved patter-matching for specific `ROLE`-types. Now it should work properly with multi-letter role-suffixes.

- `destroy` CLI action now adds option `--apply-unsafe` automatically. Option `--destroy-without-prefix` should still provide a sufficient protection from accidentally destroying everything on production.
- Dropping object types `ROLE`, `EXTERNAL TABLE`, `STAGE` is now considered "unsafe". Dropping `ROLE` prior to dropping other objects causes re-assignment of OWNERSHIP. Dropping `EXTERNAL TABLE` causes loss of associated meta-data (e.g. files, partitions), which cannot be restored easily. Dropping `INTERNAL STAGE` destroys all files in that stage.