Backporting the CI and code modifications into 2.10 for python 3.10 compatibilities

[Iximiel]

Description

@GiovanniBussi. I backported to 2.10 some modifications (CI, Fedora docker, pycv) in #1372, when this is merged @Luthaf can rebase #1348 on v2.10 and finish the pythorch update.

There will be a few merge conflict with master, I am setting up a manual merge in a next PR

Target release

I would like my code to appear in release 2.10

Type of contribution

• changes to code or doc authored by PLUMED developers, or additions of code in the core or within the default modules
• changes to a module not authored by you
• new module contribution or edit of a module authored by you

Copyright

• I agree to transfer the copyright of the code I have written to the PLUMED developers or to the author of the code I am modifying.

• the module I added or modified contains a COPYRIGHT file with the correct license information. Code should be released under an open source license. I also used the command cd src && ./header.sh mymodulename in order to make sure the headers of the module are correct.

Tests

• I added a new regtest or modified an existing regtest to validate my changes.
• I verified that all regtests are passed successfully on GitHub Actions.