Investigate and disable failing builds for >=22

[rvagg]

We seem to have some trouble producing builds with the latest v22, so unless there's easy fixes or someone shows up to deal with them we'll have to disable them entirely for >=22 builds. First, investigation into failures:

https://unofficial-builds.nodejs.org/download/release/v22.7.0/ only has musl and glibc-2.17, which is good because those are probably the most used builds. glibc-2.17 got fixed in #152 by upgrading the devtoolset to get a newer python, and musl had an alpine update that failed but was fixed by removing python2 in #153.

• loong64 is failing for strange linking errors, last build @ https://unofficial-builds.nodejs.org/logs/202408280707-v22.7.0/loong64.log. Retry just now at https://unofficial-builds.nodejs.org/logs/202409020129-v22.7.0/loong64.log - needs to be disabled.
• riscv64 is failing because I guess gcc 9 isn't supported? https://unofficial-builds.nodejs.org/logs/202408280650-v22.7.0/riscv64.log I'll queue again but am not hopefully. Probably needs to be disabled.
• x64-pointer-compression is failing with python errors, recipe probably needs updating to get a newer python somehow. Will need to be disabled until someone fixes it. Build log @ https://unofficial-builds.nodejs.org/logs/202408280614-v22.7.0/x64-pointer-compression.log

[rvagg]

Disabled in #155, if people care about these they're going to have to show up to fix them. Sorry.