2027 installer updates

[virtuald]

RobotPy currently builds the latest interpreter from source and distributes/installs that. I suspect we might want to do something slightly different for 2027 -- though, I think staying on the latest version is a good idea, which means we can't depend on the system python. Maybe we could rely on some portable Python distribution?

Ah yes, https://github.com/astral-sh/python-build-standalone might be a good candidate here?

We also will have two deploy scenarios -- one over SSH for normal development, but also a local copy/etc for on-robot development. I feel pretty strongly that the "deployed" code needs to be in its own lil place separate from where it's being edited.

#122 is relevant here too.

We also probably need to set up a mock environment for testing stuff too, since currently we don't have anything that tests whether deploy works, and it would be nice for contributors without hardware to be able to contribute.

[virtuald]

GradleRIO has some changes in the https://github.com/wpilibsuite/GradleRIO/commits/2027/ branch which will need to be copied here. Also something about setting up a systemd unit to run the robot code?

[auscompgeek]

I did some experimenting on bot earlier this week. The uv binary successfully downloaded and ran 3.13 from python-build-standalone, and I managed to create a venv and install pyntcore 2025 from PyPI and import it in the REPL.

(robotpy-venv) $ ~/.local/bin/uv pip install pyntcore
Using Python 3.13.5 environment at: robotpy-venv
Resolved 6 packages in 3.30s
Prepared 6 packages in 1.61s
Installed 6 packages in 15ms
 + pyntcore==2025.3.2.3
 + robotpy-native-ntcore==2025.3.2
 + robotpy-native-wpinet==2025.3.2
 + robotpy-native-wpiutil==2025.3.2
 + robotpy-wpinet==2025.3.2.3
 + robotpy-wpiutil==2025.3.2.3
(robotpy-venv) $ pwd
/home/systemcore

[virtuald]

I think updating the current install procedure to use python-build-standalone is the right approach for this, it works on my systemcore too.

[virtuald]

Fixed in #147