Update tutorial: Fix of installation failure of Ansible playbook due to deprecated lib2to3 module

[rhiniodontypus]

This PR implements the changes proposed in issue #6001 to fix the installation failure of the current Ansible playbook template due to the depricated Python lib2to3 module (Python >= 3.11) on Ubuntu 24.04 LTS. The main changes are:

• Added a Python and platform version check to the pre-tasks section of the galaxy.yml playbook template to install the lib2to3 package if necessary
• Updated the role versions in requirements.yml, and adjusted the Galaxy release and Miniconda versions in group_vars/galaxyservers.yml

Please review and let me know if further changes are needed.

[hexylena]

Thanks for the contribution @rhiniodontypus! And welcome to the GTN :) (Please consider adding yourself to the CONTRIBUTORS.yaml, and then also to the tutorial metadata as tester perhaps?)

Onto the content: the changes to the versions are significant, and it would require a lot of testing (there's some 15+ GAT modules downstream of this that would also need to be re-validated). We want to keep the training materials (as much as possible) in a known working state, so we generally don't update those versions unless they're running a admin training course (when other material updates happen, and testing is easier.)

If you could reduce this PR to just the pre-task that's required, then it would be much easier to merge in a short timeframe.

Otherwise, I'm not sure if there's any of the admins with time to spin up a VM, and run through each stage of the playbook + at minimum the automated testing that's available from the command line. (I wrote the 'automated' tests but I don't think any of the admin maintainers has ever run it themselves :( and I have very limited involvement currently.)

[rhiniodontypus]

Many thanks for your feedback! I totally understand the dimension of the changes.
The problem with the old settings (Galaxy release v23.0) is that it throws the error

This doesn't seem to be easily fixable because it occurs although the python3-pkg-resources package was already installed manually and therefore available at the time of deployment. The same is true for Galaxy release v.23.1.

Galaxy release v.23.2 generates a ModuleNotFoundError: No module named yaml error although python3-yaml was available at the time of deployment.

Galaxy releases v.24.0, 24.1, and 24.2 all are in conflict with the default miniconda v.23.9 setting:

Deploying the v.24 releases with the latest miniconda v25.1, however, work (if python3-lib2to3 is installed via apt).

So at the moment it is not possbile to deploy the current playbook template settings on Ubuntu 24.04 LTS without customizing the Galaxy release version and the miniconda version.
For now, I would try to continue the training with the updated versions and see if I run into any issues as the tutorial progresses. Otherwise, I will ask for a VM running Ubuntu 22.04.

Would you like me to close the PR until further notice?