python310 minimal and always download pure-python wheels

[th0ma7]

Motivation: Reduce overall python package size by remove entirely all pure-python wheels when ever possible. Using existing framework now allows to only build mandatory cross-compiled wheels and always download every pure-python wheels. This reduces considerably the package file and the overall package dependency. Using that approach python310 is now limited to the bare minimal wheels including NO cross-compiled wheels (although its configuration reflect what would be needed to compile all common cross-compiled wheels). As such every packages contains a requirement file including all its dependencies and includes all of its cross-compiled wheels to ensure supportability on every platforms.

Linked issues: #4981, https://github.com/SickChill/SickChill/issues/7672#issuecomment-985213900

Checklist

• Documentation (wiki)
• Build rule all-supported completed successfully
• Package upgrade completed successfully
• New installation of package completed successfully

Tested packages

• beets - tested on: kvmx64, armv7, armv5tel
• borgbackup - tested on: kvmx64, armv7, armv5tel
• duplicity - tested on: kvmx64, armv7, armv5tel unable to test due to gnuPG not installable
• flexget - tested on: kvmx64, armv7, armv5tel
• homeassistant - tested on: kvmx64, armv7
• mercurial - tested on: kvmx64, armv7
• python310 - tested on: kvmx64, armv7, armv5tel
• octoprint - tested on: kvmx64, armv7
• rdiff-backup - tested on: kvmx64, armv7
• sabnzbd - tested on: kvmx64, armv7
• sickchill - tested on: kvmx64, armv7, armv5tel

[th0ma7]

@hgy59 using discussion from other PR #4981 and the added flexibility now built into the framework with the recent changes I was able to easily achieve a solution merging what you where envisioning along a few details:

1. python310 is now to its simplest expression e.g. almost only cross-compiled wheels are included due to being needed in noarch packages
2. by default it now download ALL pure-python wheels. As the requirement files already allows categorizing them it was trivial to extend that to the installation methodoly
3. I've added a standard wheel installation method that greatly simplify and standardize the code in service-setup.sh

To demonstrate this I've adapted python310 + homeassistant + beets.

This has major benefits:

• all package are independent for the most part of the python310 default package wheels
• python310 becomes much simpler and provide a basic implementation
• all packages are reduced in size (as all pure-python wheels are now downloaded)

[th0ma7]

@hgy59 you where right, the only viable path is to have a python310 minimal and ensure all wheels are included in each individual packages. With all the testing I've done, unless a package only requires pure-ptyhon, I wouldn't recommend adding any cross-compiled wheels into python310 and always defer them back to the individual package as otherwise something always breaks for one or another package. With that, beets is not noarch anymore.

[th0ma7]

And forgot to mention, this to me concludes the work on the framework to fix all known python wheels issues (0.0.0, none-any, etc).

As soon as this is merge I'll publish the updated pyton310 package and will start looking at migrating any remaining python3 packages (starting with a tvheadend update). Although, unless told otherwise I'd let each maintainers to release their package updated versions (e.g. homeassistant, sickshill, etc).

[th0ma7]

@SynoCommunity/developers in process to publish python310. Not additional changes to be expected to the framework (and thnx for your patience on this). I'll let you look into your individual packages for publishing, let me know if you need assistance.