fix(release): remove bypass and enforce tag-based dynamic versioning

[eschaar]

Summary

• Removed release-time bypass override so package versioning resolves from git tags via poetry-dynamic-versioning configuration.
• Kept CI plugin installation and tag-pinned checkout flow, while removing the redundant dynamic-versioning command step.
• Updated project packaging config for cleaner Poetry/PEP 621 behavior and aligned changelog notes with the final strategy.

Why

The release pipeline must fail fast on versioning misconfiguration instead of silently producing incorrect versions.
By relying on strict tag-based configuration (including unprefixed tag matching) instead of a CI-only override, releases become deterministic and easier to reason about.

Version impact

• Patch
• Minor
• Major
• None

[Copilot]

Pull request overview

This PR tightens release-time versioning by removing a CI bypass and relying on strict, tag-based version resolution via poetry-dynamic-versioning, aiming to make releases deterministic and fail-fast on misconfiguration.

Changes:

• Updated pyproject.toml to require the dynamic-versioning plugin, enforce strict tag-based resolution, and support unprefixed SemVer tags.
• Removed the explicit poetry dynamic-versioning step from the release workflow, relying on plugin/backend behavior during build.
• Added a 1.3.6 changelog entry describing the final versioning strategy.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
pyproject.toml	Adds plugin requirements and strict/unprefixed tag configuration for dynamic versioning.
CHANGELOG.md	Documents the determinism/versioning strategy changes in a new release entry.
.github/workflows/release.yml	Removes the redundant explicit dynamic-versioning command step before poetry build.