Builds: Utilize native Mac systems for MacOS builds #53
Description
Followup to:
Currently, we utilize osxcross to cross compile the C toolchain for CGO builds targeting darwin (MacOS).
This has some problems, primarily, in chasing the dragon that is OSX security updates: we'll sort of always be a step behind depending on how osxcross stays up to date. The current build chain is nice since it's all relatively abstracted into Dagger containers but I'm thinking that keeping it there will continue to cause problems since we'll always have to cross compile from a Linux container to darwin.
At one point, I tried using the Zig zig-aarch64-macos-0.15.2 toolchain targeting Mac but ran into similar problems as #50 that didn't seem to be resolvable. Possibly worth looking at again.
osxcross also has a 2.0-llvm-based branch that uses newer LLVM cross compiling and would be much more stable. But I'm not seeing a container for that branch nor do we really want to maintain building the osxcross toolchain / container.
The fix in #50 should be a quick unlock but again, I foresee further issues as MacOS rolls out newer security patches. This likely leaves us with a difficutl choice in splitting up the Dagger build chain into 1) Linux builds on Dagger containers and 2) MacOS native builds on Mac runners.