Poetry-dynamic-versioning

* Fixed:
* There was an intermittent `ValueError` in PEP 621 mode,
related to trying to remove `"version"` from `project.dynamic`
when it had already been removed.

* Added:
* The `enable` command now supports the bypass/override environment variables
to use a different placeholder version than 0.0.0.
* Fixed:
* The `enable` command would add `"version"` to `project.dynamic` even if it were already present.
([Contributed by waketzheng](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/214))
* The `enable` command would set `tool.poetry.version` to `"0.0.0"`
even if the field were already present with a different value.

* Added:
* CLI: `show` command to print the version without changing any files.

* Fixed:
* The formatting of `project.dynamic` and `tool.poetry.version`
could be changed when triggering the plugin via `poetry dynamic-versioning` or `pip install`
(but not via `poetry build` or `poetry-dynamic-versioning`).

* Fixed:
* Array formatting was not preserved when changing `project.dynamic` in pyproject.toml.
([Contributed by edgarrmondragon](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/207))

* Added:
* CLI: When pyproject.toml contains the `project` section,
the `enable` command will add the required fields for Poetry 2.0.0+.
* Fixed:
* For compatibility with Poetry 2.0.0,
adjusted Poetry constraint from `^1.2.0` to `>=1.2.0`.
* For compatibility with Poetry 2.0.0,
when inserting the dynamic version into pyproject.toml with PEP 621 mode activated,
the plugin ensures not to set `project.version` and `tool.poetry.version` at the same time.
* An `UnboundLocalError` could happen when pyproject.toml was misconfigured.