Build binaries for stackablectl

[sbernauer]

This is needed, so that we can switch from the old stackablectl to the new one. Currently the Windows build is broken. Currently investigated as part of #98 and #111

### Tasks
- [X] https://github.com/stackabletech/operator-rs/pull/635
- [x] https://github.com/stackabletech/stackable-cockpit/pull/93
- [ ] Build binaries for Windows
- [x] Build binaries on release and add them to the GitHub release

[Techassi]

Okay, after several hours of going down rabbit holes, here is the current status:

• The environment variable CC cannot contain any spaces in the supplied path. This is due to cgo not being able to handle the spaces without escaping. The fix for this is to add single quotes ' around the C compiler path. This error only gets uncovered when working with Windows, as it places the C compiler in C:\Program Files\.... This can be fixed by patching gobuild. See here. This ideally should be fixed upstream, but the project seems unmaintained. Another option is to fix it in a fork.
• msys2 is needed, as otherwise the build process fails with cl.exe not being able to parse the /Werror argument. This is still weird, as there is no proper support for MSVC builds.
• The target x86_64-windows-msvc straight up doesn't work (because cgo doesn't support it). Trying to use the MSVC target fails with multiple weird errors which look important, but are not related to the issue at all. See here for more context.
• Unresolved libs: ld.exe cannot find -lresolv. This cannot be fixed by installing host dependencies bit it seems like it can be fixed by removing the cargo flag cargo:rustc-link-lib=resolv. This seems to be related to changes to cgo in Go 1.20. More context here.

There seems to be one (hopefully) final issue which prevents us from building for Windows: rust-lang/rust#112368. One suggested fix didn't work and I didn't try the alternative approach. This should be resolved by either using an up2date binutils version or waiting for a new Rust GNU toolchain.