Motivation

#10127 introduced dependency pinning.
This is a good opportunity to revisit current pins in the setup.cfg and try to upgrade as much as possible, as well as to remove some safety pins which have just defined to avoid breaking changes in the future (which is not necessary, because this only happens in a dedicated PR now).

Changes

• Removes as many version pins in the setup.cfg as possible and updates the pins.
  • Currently the only remaining pins are:
    • moto-ext - explicitly updated when we create a release of our moto fork
    • dill - iirc this should be pinned to avoid a breaking change? /cc @giograno
    • botocore - explicitly updated with ASF updates, see pin botocore with ASF API updates, add ASF API forward compatibility #10183
    • docker - waiting for a release of 7.0: Docker Tag Parsing Issue with Registry Ports docker/docker-py#3195 / fix: tag regex should allow ports docker/docker-py#3196
    • black - limited to the major version 23 to avoid lots of reformatting, should be upgraded separately or replaced with ruff format
    • jsonpath-ng - has been pinned with Pin jsonpath_ng to 1.5.3 to unblock CI #9142, breaks skip verification handling in snapshot library (test_dot_in_skip_verification_path) /cc @dominikschubert
    • antlr4-python3-runtime - the antlr4 runtime is tightly coupled to the generated code. The pin will remain for now, and once the generation is automated, we can automate version upgrades. See remove pins in setup.cfg, add .python-version #10195 (comment).
• Reintroduces a .python-version file.
  • This is getting more important after the introduction of the dependency pinning because the dependencies can differ between python versions and the python version used to generate the lock files is recorded in the lock file itself.

TODO

• Check failures in the test pipeline (also make sure to execute downstream pipelines).
  • There are 4 remaining test failures in the pipeline testing the pro integration. These are related to the upgrade of the test naming to pytest 8: 6105fed
  • This means that this PR will cause integration issues which will be resolved by upgrading to pytest 8 there as well.
  • Another option would be to duplicate the snapshot data for both naming styles, but I don't think this is necessary.
• Maybe circle back on pins which are still necessary (and inform service owners + add comments).
  • After several iterations, we identified the minimum needed pins (as listed above).