[PIP] Update packaging requirement from <24,>=20.0 to >=20.0,<25 in /pulp-glue

[dependabot]

Updates the requirements on packaging to permit the latest version.

Release notes

Sourced from packaging's releases.

24.1

What's Changed

• pyupgrade/black/isort/flake8 → ruff by @​DimitriPapadopoulos in pypa/packaging#769
• Add support for Python 3.13 and drop EOL 3.7 by @​hugovk in pypa/packaging#783
• Bump the github-actions group with 4 updates by @​dependabot in pypa/packaging#782
• Fix typo in _parser docstring by @​pradyunsg in pypa/packaging#784
• Modernise type annotations using FA rules from ruff by @​pradyunsg in pypa/packaging#785
• Document markers.default_environment() by @​edgarrmondragon in pypa/packaging#753
• Bump the github-actions group with 3 updates by @​dependabot in pypa/packaging#789
• Work around platform.python_version() returning non PEP 440 compliant version for non-tagged CPython builds by @​sbidoul in pypa/packaging#802

New Contributors

• @​dependabot made their first contribution in pypa/packaging#782
• @​edgarrmondragon made their first contribution in pypa/packaging#753

Full Changelog: pypa/packaging@24.0...24.1

Changelog

Sourced from packaging's changelog.

24.1 - 2024-06-10

No unreleased changes.
24.0 - 2024-03-10

• Do specifier matching correctly when the specifier contains an epoch number and has more components than the version (:issue:683)
• Support the experimental --disable-gil builds in packaging.tags (:issue:727)
• BREAKING: Make optional metadata.Metadata attributes default to None (:issue:733)
• Fix errors when trying to access the description_content_type, keywords, and requires_python attributes on metadata.Metadata when those values have not been provided (:issue:733)
• Fix a bug preventing the use of the built in ExceptionGroup on versions of Python that support it (:issue:725)
• Support creating a SpecifierSet from an iterable of Specifier objects (:issue:775)

23.2 - 2023-10-01

* Document calendar-based versioning scheme (:issue:`716`)
* Enforce that the entire marker string is parsed (:issue:`687`)
* Requirement parsing no longer automatically validates the URL (:issue:`120`)
* Canonicalize names for requirements comparison (:issue:`644`)
* Introduce ``metadata.Metadata`` (along with ``metadata.ExceptionGroup`` and ``metadata.InvalidMetadata``; :issue:`570`)
* Introduce the ``validate`` keyword parameter to ``utils.normalize_name()`` (:issue:`570`)
* Introduce ``utils.is_normalized_name()`` (:issue:`570`)
* Make ``utils.parse_sdist_filename()`` and ``utils.parse_wheel_filename()``
  raise ``InvalidSdistFilename`` and ``InvalidWheelFilename``, respectively,
  when the version component of the name is invalid
* Remove support for Python 3.7 (:issue:`783`)
23.1 - 2023-04-12

• Parse raw metadata (:issue:671)
• Import underlying parser functions as an underscored variable (:issue:663)
• Improve error for local version label with unsupported operators (:issue:675)
• Add dedicated error for specifiers with incorrect .* suffix
• Replace spaces in platform names with underscores (:issue:620)
• Relax typing of _key on _BaseVersion (:issue:669)
• Handle prefix match with zeros at end of prefix correctly (:issue:674)

23.0 - 2023-01-08

* Allow ``"extra"`` to be ``None`` in the marker environment (:issue:`650`)
</tr></table> 

... (truncated)

Commits

• 85442b8 Bump for release
• 3e67fc7 Work around platform.python_version() returning non PEP 440 compliant versi...
• 32deafe Bump the github-actions group with 3 updates (#789)
• e0dda88 Document markers.default_environment() (#753)
• cc938f9 Modernise type annotations using FA rules from ruff (#785)
• 757f559 Fix typo in _parser docstring (#784)
• ec9f203 Bump the github-actions group with 4 updates (#782)
• 5cbe1e4 Add support for Python 3.13 and drop EOL 3.7 (#783)
• cb8fd38 pyupgrade/black/isort/flake8 → ruff (#769)
• e8002b1 Bump for development
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[patchback]

Backport to 0.29: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 6e9a634 on top of patchback/backports/0.29/6e9a6341bc9576071af2036993b2829f25547ccd/pr-1071

Backporting merged PR #1071 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulp-cli.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/0.29/6e9a6341bc9576071af2036993b2829f25547ccd/pr-1071 upstream/0.29

4. Now, cherry-pick PR [PIP] Update packaging requirement from <24,>=20.0 to >=20.0,<25 in /pulp-glue #1071 contents into that branch:

   $ git cherry-pick -x 6e9a6341bc9576071af2036993b2829f25547ccd

   If it'll yell at you with something like fatal: Commit 6e9a6341bc9576071af2036993b2829f25547ccd is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 6e9a6341bc9576071af2036993b2829f25547ccd

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [PIP] Update packaging requirement from <24,>=20.0 to >=20.0,<25 in /pulp-glue #1071 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/0.29/6e9a6341bc9576071af2036993b2829f25547ccd/pr-1071

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.