UPDATE: I've been convinced by krish and alex2101 that moving to python3.9 is the next logical step. And then potentially we can make the change to 3.10 after this work is done. Original bug report follows:

It would be a good idea to make python 3.10 the default in 'next' release ASAP so we can start to work out the kinks. This would involve several steps and these are the steps I'm considering:

• Make python-kit an autogenerated instead of indy kit. this requires updates to kit-fixups/foundations.yaml and I need to migrate the location of the kit on code.funtoo.org (from one project to another)
• Add python-3.10 ebuilds to kit-fixups/python-kit/next.
• Add python USE settings to kit-fixups/foundations.yaml for next release.
• (OPTIONAL) See if we need any profiles changes for next-release. These may get added to a forked set of profiles in core-kit/next/profiles and I will need to check autogens to make sure we use them

At this point, we should have things in place to start to mess with python 3.10 and can make sure that portage, ego and friends are working OK. If we break things along the way, this is OK as long as the breakage is relatively temporary so it does not impact riscv significantly.