py3-tomli cleanup

[pnasrat]

py3-tomli is only needed on py3.10 and below, the upstream recommends usingcompat code for builtin in tomllib import

Post #20318 should cleanup this extraneous dep for python >= 3.11

• Make build with version streams to git-checkout
• Cleanup dependencies using py3-tomli with compat layer
• File upstream fix for mlflow
• File upstream fix for semgrep

https://github.com/hukkin/tomli?tab=readme-ov-file#building-a-tomlitomllib-compatibility-layer

• gi-docgen.yaml https://gitlab.gnome.org/GNOME/gi-docgen/-/blob/2024.1/gidocgen/config.py#L9
• mlflow.yaml looks like only for clint https://github.com/search?q=repo%3Amlflow%2Fmlflow+tomli&type=code
• pip-zipapp.yaml https://github.com/pypa/pip/blob/d94806f9592f03cc092079f4517039ea6c1b2e0e/src/pip/_vendor/pyproject_hooks/_compat.py#L6
• py3-gpep517.yaml https://github.com/projg2/gpep517/blob/ebcb7a9cb6129375d4a88a9d941165dbc5b728fa/gpep517/__main__.py#L28
• py3-hatch.yaml https://github.com/pypa/hatch/blob/d73037fe7e9b66eeeba2e72d37074373594221c5/src/hatch/utils/toml.py#L6 NEEDS tomli-w for saving config
• py3-maturin.yaml https://github.com/PyO3/maturin/blob/894231c644c2d7a9a31349c86b3f3c431b74d615/maturin/__init__.py#L25
• py3-meson-python.yaml https://github.com/mesonbuild/meson-python/blob/4f50bf27ef5282f8147c1df073d27859bda5e890/mesonpy/__init__.py#L42
• py3-pep517.yaml only used in test suite https://github.com/pypa/pyproject-hooks/blob/261e4d82121782d05f6fddfaded8b8a7493d0370/dev-requirements.txt#L5
• py3-pytest.yaml https://github.com/pytest-dev/pytest/blob/329d3712146e69c471be3e30883d54bdde2f76cb/pyproject.toml#L48
• py3-setuptools-scm.yaml (from v7.1.0 onward) https://github.com/pypa/setuptools_scm/blob/234b74fd9cf847baaac52a195d1ff4f59ed94c8c/src/setuptools_scm/_integration/toml.py#L14
• py3-tomli-w.yaml (sibling project to tomli for writing toml)
• semgrep.yaml setuptools install_requires for tomli but looks like it moved from directly using tomli to parsy in semgrep/semgrep@4fc248d so may not actually require. Possibly fix upstream