Ahjo

Bug Fix: Documented extended properties can contain non-ASCII characters
Action `update-file-obj-prop` stores all extended properties of objects in schemas listed in variable `metadata_allowed_schemas`. Extended properties are stored to JSON files with encoding UTF-8. These files can contain non-ASCII characters.

Improvements to handling of extended properties (Sql Server)
Ahjo includes an action that stores extended properties into files. At the end of `deploy` action, these documented extended properties are updated to database. Documented and updated schemas can be controlled with variable `metadata_allowed_schemas`.

Older versions of Ahjo supported documenting and updating only extended properties with name "Description". In this version, the name restriction is removed and all extended properties can be documented and updated. To better support documenting multiple extended properties, the file format is changed from CSV to JSON.

Action `update-csv-obj-prop` is renamed to `update-file-obj-prop`.

Remove `ahjo_path` from Context
`ahjo_path` is removed from Context class. If you need the path to packages' root, you can import it from context module.

from ahjo.context import AHJO_PATH

`ahjo_path` parameter is removed from function `operations.tsql.db_object_properties.update_db_object_properties`.

Fetch "Git version" with `git describe` command
At the end of `deploy` action, the current remote repository url (origin), branch name and commit hash are stored to database.
In older versions of Ahjo, this table had three columns:
- `Repository`
- `Branch`
- `Commit_hash`

In this version, the `Commit_hash` column has been renamed to `Commit` and the column now stores "Git version"- a "human-readable" object name that identifies commit or tag. This object is fetched with command `git describe --always --tags`.
Ahjo automatically renames the `Commit_hash` column, when `deploy` action is run.

Update project structure and development tools
- Source code moved under directory `src`
- Added `pyproject.toml` and `setup.cfg`
- Versioning is handled with [setuptools-scm](https://pypi.org/project/setuptools-scm/)

This version offers no change in functionality of Ahjo.

Drop action
New `drop` action drops all views, procedures, functions, clr-procedures and assemblies that are listed in directory *./database* with TRY-CATCH.

Bug Fix: Ahjo crashes when log file rotates
Fixed a bug that caused Ahjo to crash when log file rotated. The bug existed when Ahjo and Alembic had separate logging configurations (and handlers) writing to same log file. In current solution, Alembic operations are executed using Alembic API and existing Alembic config is altered such that Alembic will use Ahjo's logging configuration.

Bug Fix: deploy_sqlfiles - do not show irrelevant errors
Fixed a bug that caused all surfaced errors to be shown at the end of `deploy_sqlfiles` execution, even if some of the objects had been deployed successfully. Current solution displays and logs only errors related to failed objects.