Investigate support for building RoboStack distributions for multiple Python minor versions

Until now, each RoboStack distribution (or more technically, each full rebuild/sync) has been built for a single Python version, to limit the maintainer load. While changing this requires discussion, in this issue I would like to at least investigate the technical changes that are required to permit (in theory) to build a given RoboStack full rebuild/sync for multiple Python versions.

Why I am interested in this? In my organization sometimes we are forced to use a specific Python version, that is typically given by a software that it is only available for a specific Python versions. Examples includes:

• Blender, for which each version is tightly connected to a Python version (as of July 2025 Python 3.11)
• Each version of IsaacSim/IsaacLab is tightly connected to a release of the (closed source) Omniverse Kit, that in turns is only available for a given Python version (as of July 2025 Python 3.11)

So for example, in this specific time I would like to have fresh releases of ROS packages available for Python 3.11, but on the other hand some users are interested in having packages built for newer Python versions (see https://github.com/RoboStack/robostack.github.io/issues/76). Compatibly with maintainers load, it would be great to have at least a couple Python versions available for each RoboStack's full rebuild/sync.

Start by tracing how a RoboStack full rebuild/sync currently selects and builds its single Python version, then identify the assumptions that prevent multiple minor versions. Done means documenting the required technical changes, constraints, and a feasible approach for supporting at least two Python versions, without committing to the final policy.