[24.1] Add galaxy metapackage for installing the latest stable version of Galaxy with pip install galaxy

[natefoo]

This pins versions of all the galaxy* packages, but to mimic the current production best practice/run.sh, should we add all of pinned-requirements.txt? yes

I tried adding all of pinned-requirements.txt to install_requires but it fails because galaxy-data 24.1.2 (and all earlier versions of it) have a pin on social-auth-core==4.0.3 while the pinned-requirements.txt version for 24.1.2 is 4.5.4. We should unpin this in galaxy-data but it won't be possible to build a fully pinned galaxy metapackage until we unpin that and publish 24.1.3 packages.

How to test the changes?

(Select all options that apply)

• Instructions for manual testing are as follows:

  cd package/galaxy
  python -m build
  pip install --extra-index-url https://wheels.galaxyproject.org/simple ./dist/galaxy-24.1.2-py3-none-any.whl

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[mvdbeek]

Are there tools to keep this up to date ?

[natefoo]

No, I guess it should be part of the package release process?

[jdavcs]

Yep, this could be handled as part of create_point_release in https://github.com/galaxyproject/galaxy-release-util/blob/main/galaxy_release_util/point_release.py#L597
Is this is a subset of pinned-requirements.txt? (I assume it's the difference between that and the union of requirements for all other packages?)

[jdavcs]

☝️ and I can add that to galaxy-release-util unless you'd like to handle it.

[natefoo]

galaxyproject/galaxy-release-util#23