Poetry-dynamic-versioning

* Added:
* The plugin now supports Poetry's upcoming PEP-621 functionality.
More info here: https://github.com/python-poetry/poetry/issues/3332

If your pyproject.toml defines `tool.poetry.name`,
then the plugin will preserve its existing behavior.

However, if your pyproject.toml:

* does not define `tool.poetry.name`
* defines `project.name`
* defines `project.dynamic` to include `"version"`
* does not define `project.version`

...then the plugin will enable its PEP-621 functionality.

Because PEP-621 support is not yet released and finalized in Poetry itself,
it is also subject to change in the plugin.

([Prototyped by edgarrmondragon](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/181))

* Added:
* `pattern-prefix` option to add a prefix to the version tag pattern.
* `ignore-untracked` option to control the detection of dirty state.
* `from-file` config section to read a version from a file instead of the VCS.
* `POETRY_DYNAMIC_VERSIONING_DEBUG` environment variable for some logging.
* Changed:
* Updated Dunamai to 1.21.0+ for the latest features.

* Added:
* `initial-content-jinja` option in `tool.poetry-dynamic-versioning.files` section.
* Fixed:
* Line ending style was not preserved in some cases because of the default behavior of `pathlib.Path.read_text`.
To avoid this, `pathlib.Path.read_bytes` is used instead now.
([Contributed by nardi](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/157))

* Fixed:
* Custom substitutions in pyproject.toml weren't cleaned up correctly.
This was because the plugin would record the "original" content of the file
after the `version` and `enable` fields had already been changed.
Now, substitutions are reverted first before reverting `version` and `enable`.

* Added:
* `tool.poetry-dynamic-versioning.files` config section.
This allows you to create a file in a default state before applying substitutions to it.
You can also leave the substitutions in place when the plugin deactivates.

* Fixed:
* Compatibility with poetry-core 1.7.0, which removed the `poetry.core.semver` module.
* The `enable` command now constrains the plugin version to `>=1.0.0,<2.0.0`
to protect against any potential API changes.