info: require pkginfo >= 1.12 for METADATA 2.4 support and loosen check for unknown METADATA versions

[radoering]

Pull Request Check List

Resolves: #9885

• Added tests for changed code.
• Updated documentation for changed code.

I think we should do a 1.8 release, which requires pkginfo >= 1.12 to reduce support workload.

Further, after some testing I agree to @Secrus' proposal to loosen the check for unknown METADATA versions.

We introduced this check because pkginfo < 1.11.0 did not handle unknown versions well:

>>> print(pkginfo.Wheel("demo_metadata_version_299-0.1.0-py2.py3-none-any.whl").requires_dist)
()

However, pkginfo >= 1.11.0 handles it better:

>>> print(pkginfo.Wheel("demo_metadata_version_299-0.1.0-py2.py3-none-any.whl").requires_dist)
['cleo; extra == "foo"', 'pendulum (>=1.4.4)', 'tomlkit; extra == "bar"']
NewMetadataVersion: New metadata version (2.99) higher than latest supported version: parsing as 2.3

[Secrus]

LGTM, thank you for tackling this issue.

[poetry-bot]

The backport to 1.8 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.8 1.8
# Navigate to the new working tree
cd .worktrees/backport-1.8
# Create a new branch
git switch --create backport-9888-to-1.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a3cae0cb2676bc6408f7205f167fbf4abf72d0be
# Push it to GitHub
git push --set-upstream origin backport-9888-to-1.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.8

Then, create a pull request where the base branch is 1.8 and the compare/head branch is backport-9888-to-1.8.