I don’t think that’s really useful before https://github.com/JuliaLang/julia/issues/41440 is resolved. That’s the main stumbling block at the moment. All tests jobs are going to segfault because of that, it isn’t incredibily useful to run jobs that systematically crash for a well known issue. The problem is that that’s not trivial to address.
Additionally, most (but not all?) Julia CI runs on on-premise hardware, I’m not sure renting overpriced cloud machines is the best option money-wise. M1 boxes may already be in the availability of the developers, but until someone takes the time to solve https://github.com/JuliaLang/julia/issues/41440 there is not much need to use them.
That said, also on-premise CI has a non-zero cost, so supporting the project is a good idea anyway.