Ok, I can reproduce the MAVSDK-Python pip issue:
python3 -m pip install --upgrade mavsdk
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: mavsdk in ./.local/lib/python3.10/site-packages (1.4.9)
Requirement already satisfied: aiogrpc>=1.8 in ./.local/lib/python3.10/site-packages (from mavsdk) (1.8)
Requirement already satisfied: grpcio>=1.50.0 in ./.local/lib/python3.10/site-packages (from mavsdk) (1.51.1)
Requirement already satisfied: protobuf<=3.20.1 in ./.local/lib/python3.10/site-packages (from mavsdk) (3.20.1)
It looks like the linux wheels are missing: mavsdk · PyPI
Aha, it turns out the file is too large, presumably because we added in the debug symbols:
A fix is coming with CI: don't include debug symbols for musl builds by julianoes · Pull Request #2217 · mavlink/MAVSDK · GitHub where we omit the debug information. After that I’ll trigger MAVSDK-Python v2.0.1.