Migrate build system from Poetry to Hatchling with dynamic versioning

[Copilot]

Removes the hardcoded version and migrates pyproject.toml from Poetry to Hatchling, using hatch-vcs to derive version from git tags — matching the pattern used in pmultiqc.

Changes

• Build system: poetry-core → hatchling + hatch-vcs
• Version: Hardcoded version = "0.0.27" → dynamic = ["version"] sourced from VCS tags
• Metadata format: [tool.poetry] → PEP 621 [project] with updated author syntax
• Dependencies: [tool.poetry.dependencies] → [project] dependencies array
• Entry points: [tool.poetry.urls/scripts] → [project.urls] / [project.scripts]
• Hatch config: Added [tool.hatch.version], [tool.hatch.version.raw-options] (local_scheme = "no-local-version"), and [tool.hatch.build.targets.wheel]

[ypriverol]

@copilot the version have to be encoded in someway; because the recipe is failing: https://github.com/bigbio/quantms-utils/actions/runs/23748956530/job/69185245147

[Copilot]

@copilot the version have to be encoded in someway; because the recipe is failing: https://github.com/bigbio/quantms-utils/actions/runs/23748956530/job/69185245147

The conda recipe was missing hatch-vcs in its host build requirements — hatchling was present but the VCS plugin needed to resolve the dynamic version wasn't installed, causing the Unknown version source: vcs error. Fixed in commit 1880496 by:

• Adding hatch-vcs to the host requirements in recipe/meta.yaml
• Updating the recipe version to 0.0.27