Pin twine and hatchling versions

[jj22ee]

Issue #, if available:
Address release failure: https://github.com/aws-observability/aws-otel-python-instrumentation/actions/runs/18734463348/job/53438678131

1. hatchling is responsible for generating a metadata file included in the wheel file.
2. twine will validate this metadata before publishing to PyPI.

According to the release failure, the metadata's license-expression field is malformed. Yet I tried testing an artifact in a fork, but the wheel file's metadata doesn't look suspicious. So the exact root cause is unknown.

Description of changes:
Pins the following for the release:

twine==5.1.1
hatchling==1.25.0

The latest versions are not compatible with the release process, but note that

• last twine release was on September 4th, 2025 - https://pypi.org/project/twine/#history
• last hatchling release was on December 15th, 2024 - https://pypi.org/project/hatchling/#history
• Our latest ADOT Python release was on September 16th.

Since there have been no new releases from twine/hatchling recently, it is suspected (but not confirmed yet in order to get this release out asap) that before the GitHub actions/setup-python upgrade in #506, an older pip version was installed, which installed older compatible versions of twine/hatchling. Probably since we upgraded actions/setup-python, pip might now install the latest versions of them, in which our repo is not yet compatible according to the failed release.

Reasoning why we need both (test publish to TestPyPI):

• failure with only pinning twine: https://github.com/aws-observability/aws-otel-python-instrumentation/actions/runs/18762260003/job/53529721289
• failure with only pinning hatchling: https://github.com/aws-observability/aws-otel-python-instrumentation/actions/runs/18762938622/job/53531893352
• success by pinning both twine and hatchling: https://github.com/aws-observability/aws-otel-python-instrumentation/actions/runs/18763023516/job/53532160232

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.