chore: build argoexec on windows 2022 & 2025

[mweibel]

Motivation

New major windows version is out and we'll be testing the version soon.

Modifications

Adjusted release build to build on windows 2022 and windows 2025 while also adjusting the generated manifest.

Verification

Couldn't test it since it's a GitHub runner adjustment.

[mweibel]

should I, as a test, adjust the rules when to build the pipeline or do you have already an established way in place to test changes to github workflows?

[tico24]

It would be more common to adjust on your fork to test so that you can demonstrate it works.

[mweibel]

@tico24 I adjusted the workflow so it can run - the build was successful but due to missing secrets I of course couldn't push the image.

https://github.com/helio/argo-workflows/actions/runs/13303462419/job/37149113756

does that suffice?
Otherwise I could probably rename the branch to start with dev-* and it would run the workflow here, too. Would you prefer that?

[mweibel]

oh, I'm sorry. I just saw something upon doing a deeper inspection. Need to verify it actually works.

indeed - latest build fails: https://github.com/helio/argo-workflows/actions/runs/13329479489/job/37230045905
we've had similar issues just today with other docker images. Might have to do with the windows revision. Will clarify this and possibly update what is needed.