windows: Use prebuilt gvproxy/win-sshproxy binaries

[cfergeau]

Since gvisor-tap-vsock 0.7.1, the upstream project ships pre-built
Windows binaries for gvproxy and win-sshproxy. These binaries are built
with -Hwindowsgui as needed by podman.

This makes the same change in winmake.ps1, but I had to hardcode
gvisor-tap-vsock version in one more place.

Does this PR introduce a user-facing change?

None

[rhatdan]

@n1hility @ashley-cui @baude PTAL

[baude]

LGTM

[n1hility]

Looks good other than the minor issue

[ashley-cui]

Do we want to keep both targets in the .ps1 just in case a user wants to build gvproxy off main, or do you think that won't be a use case?

[cfergeau]

Do we want to keep both targets in the .ps1 just in case a user wants to build gvproxy off main, or do you think that won't be a use case?

I don't think this will be needed very often/at all so I would not keep it. Easy to revert/rework if this turns out to be needed. Rebuilding one of these binaries from git can be done with a one-liner: GOOS=windows go install -ldflags -H=windowsgui github.com/containers/gvisor-tap-vsock/cmd/[email protected]

[ashley-cui]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfergeau, n1hility

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [n1hility]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[n1hility]

/lgtm