chore: update flit-core requirement from <4,>=3.2 to >=3.12.0,<4 in the python-packages group across 1 directory

[dependabot]

Updates the requirements on flit-core to permit the latest version.
Updates flit-core to 3.12.0

Changelog

Sourced from flit-core's changelog.

Release history

Version 4.0

This version contains breaking changes, but most projects which are already using the [project] table for metadata shouldn't be affected, and can simply change the flit_core <4 constraint to <5.

• The [tool.flit.metadata] table is no longer used for project metadata (:ghpull:771). Use the newer :ref:[project] table <pyproject_toml_project> instead (or if that is not possible, build with flit_core <4).
• :ref:build_cmd and :ref:publish_cmd no longer include files in the sdist based on what is committed in git or Mercurial (:ghpull:772). These commands now build packages more like Flit does when called as a backend by e.g. python -m build. Specify :ref:sdist include & exclude patterns <pyproject_toml_sdist> instead (Flit can help to generate these), or pass the --use-vcs option to get the old behaviour back.
• flit_core now requires Python 3.8 or above (:ghpull:738)
• The --setup-py option to generate sdists containing a setup.py file is no longer available (:ghpull:776).
• Making typing stubs packages with a -stubs suffix will now work (:ghpull:742).
• The default glob patterns for license files have been extended to include NOTICE* and AUTHORS* (:ghpull:758).
• license-files glob patterns can contain spaces (:ghpull:797).
• Fix a bug where license files could be found twice on Windows (:ghpull:752).
• The new Import-Name and Import-Namespace metadata fields (metadata 2.5) are now supported (:ghpull:774). In most cases no new input is required, as Flit will create this metadata automatically.
• Fix creating RECORD files when file names include commas (:ghpull:744).
• The --use-vcs option now correctly recognises git from inside a git worktree folder (:ghpull:799).
• On Python 3.12 and above, flit build now uses the 'data' filter when extracting the just-created sdist prior to building a wheel (:ghpull:775). This restricts some special features of tar files, but sdists are unlikely to use these features, and they would probably break in other scenarios if you did.
• The vendorised readme_renderer package was updated to version 44.0 (:ghpull:760).

Version 3.12

• Support for license expressions using the AND and OR operators (:ghpull:731).
• Recognise __version__: str = "0.1" annotated assignments when finding the version number (:ghpull:728).
• Clear error message when referring to a license file in a parent directory,

... (truncated)

Commits

• 1c81417 Merge pull request #737 from pypa/changelog-3.12
• d9ce4c6 Bump version: 3.11.0 → 3.12.0
• 27ea098 Prepare release notes for 3.12
• 7a6e9b2 Merge pull request #731 from AA-Turner/compound-spdx
• 0b07d23 Reword error messages
• 38429c9 Add empty expression test case
• 4ab2335 Add brackets-only test case
• 78db7b5 Shorten error messages
• 20e1729 Handle mixed-case licence operators
• 9bd1477 Raise error on expressions with no operator
• Additional commits viewable in compare view

[dependabot]

Assignees

The following users could not be added as assignees: overcat. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.