GitHub Actions CI: Remove Zig in Python wheel release

[jayaddison]

The Zig toolchain functionality enabled here originates from a build workflow in the uap-rust repository; as far as I can tell, Zig is not required when building and releasing the Python wheels.

My understanding is that the maturin-action that installs the Zig dependencies would proceed even if they cannot be installed, so I don't think that their failure would block the release process here.

Even so, I think that software build processes should usually try to limit their build requirements to only what is necessary, so I'm offering this as a cleanup.

Resolves #312.

[jayaddison]

@masklinn hm. re-reading the maturin-action link I posted -- I noticed that containerisation gets turned off as a side-effect of the --zig argument.

It looks like the CI job assigns various native build runners from a matrix of options -- so I don't know whether we need the overhead (and extra surface area) of a Docker build.

One idea would be to explicitly configure container: off for these builds, to retain equivalence with the side-effect that the --zig arg had.

[masklinn]

hm. re-reading the maturin-action link I posted -- I noticed that containerisation gets turned off as a side-effect of the --zig argument.

That was never intended, so doesn't matter.

It looks like the CI job assigns various native build runners from a matrix of options -- so I don't know whether we need the overhead (and extra surface area) of a Docker build.

The question is less whether we need the overhead and more whether we need to avoid it.

The wheels workflow doesn't run normally, only when the PR is flagged to run it or when cutting a release, so it doesn't matter.

[masklinn]

Although it does look like the dockerised maturin is not happy: https://github.com/ua-parser/uap-python/actions/runs/25629265798/job/75229894764#step:5:262