Translate C workarounds

[MasonRemaley]

I cached c.zig in the repo so that I could manually work around some translate C issues. Most (all?) of them have been patched now.

Once we upgrade this library to a new stable release of Zig that includes the patches--or start using Translate C as an external package--we should remove the cached c.zig and just generate it as part of the build process.

[MasonRemaley]

This is pending on two upstream issues being resolved:

• Translate C failing to pull in libc on nixos
• Issue with some Pipewire static asserts
  • I've worked around this one locally, so it's not technically blocking
  • This open PR resolves the issue

In the mean time, I'm going to set up translate C support behind a flag, to make repros and migrating away from the cached c.zig file easier.

I've decided to remove c.zig despite this issues, since you can work around it by adding libc to your nix flakes. I don't think this should be necessary, but it's easier to use the workaround for now than to maintain the cached results in c.zig.

I'll rename this issue and keep it open until no workaround are necessary.

[mgerb]

I'm in the process of upgrading my project to Zig 0.16.0 and ran into the NixOS libc issue. Adding libc to my flake fixed the stdio.h compiler error, however it caused a libc symbol lookup error at run time. I suspect it was due to a version mismatch.

I managed to work around the issue for now by removing libc from my flake and then specifying the glibc_version for my standard target.

e.g.

    const target = b.standardTargetOptions(
        .{
            .default_target = .{
                .glibc_version = .{ .major = 2, .minor = 42, .patch = 0 },
            },
        },
    );