Licensing requirements for VMs and lack of server hardware that can be put in datacenters are both obstacles to target Apple Silicon. Not insurmountable, you can build enclosures for a rack of Mac Studios & Mac Pros and orchestrate VMs with Hypervisor framework, but it's a large enough obstacle that major cloud providers don't offer it and that pushes large costs onto the CI providers, which then get pushed to the folks trying to build tooling that works on M1 Macs. That includes the open source ecosystem.
The alternative is cross compilation, either cross-arch or cross-platform or both. All of these options are brittle and complex.
Speaking from experience here, I've had to follow issue trackers for: programming language teams shipping parity for M1, major libraries (think of foundational libraries like GRPC's libraries for each language) not yet shipping binaries for M1, and developer tools and OSS teams producing binaries. All of this needs to come together, and it hasn't yet.
The whole ecosystem is straining under the weight of this complexity to target engineers' laptops.