build(deps): bump pyroma from 2.6 to 4.2

[dependabot]

Bumps pyroma from 2.6 to 4.2.

Changelog

Sourced from pyroma's changelog.

4.2 (2023-02-25)

• Fall back to installing project's build backend in an isolated environment if a compatible version isn't installed in the current env [CAM-Gerlach]

• Fix metadata extraction failure when project long_description is included as a header rather than a payload in the METADTA file [CAM-Gerlach]

• Add a fallback to restore compatibility with Setuptools <61 [CAM-Gerlach]

• Fix tests failing due to invalid versions on Setuptools >=66 [CAM-Gerlach]

• Add python_requires, update classifiers, add implicit dependencies and remove unused deps in Pyroma's own packaging metadata [CAM-Gerlach]

4.1 (2022-11-24)

• Moved from a custom trove classifiers list to using the trove-classifiers package [hugovk]

• Support checking the Requires-Python metadata [davidandreoletti]

• Silence noisy build backend output when building metadata [CAM-Gerlach, wesleybl]

• Official support for Python 3.11 [hugovk, radarhere]

• Some string formatting bugs [hugovk, CAM-Gerlach]

• Now follows black and flake8 rules

• Check if author_email field contains author name [bessman]

4.0 (2022-04-14)

• No changes from 4.0b2.

4.0b2 (2022-03-29)

• The deprecation test for test_suite is no longer needed, as the patched setuptools method of gathering metadata as a whole is deprecated.

• description_content_type also needs a mapping in the metadata map.

... (truncated)

Commits

• 763bfde Preparing release 4.2
• 3935808 Fall back to isolated mode for metadata build & simplify codepath (#92)
• 56f3706 Make sure release uplaods a wheel
• 1351bec Back to development: 4.2
• 28387e8 Preparing release 4.1
• 6f3ed99 Got the pep621 test running again
• 837b29e End of file fix
• 265b29d Updated CHANGES.txt
• 3b2e676 Merge branch 'bessman-pep621_author_name'
• 2c8a893 Stripped a stray space
• 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 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)