bug: Release workflow should play nice with GitHub Packages

[cychiang]

Describe the bug

The kcp and syncer should use the same release version. In the release page, we can find the correct version of kcp and kubernetes-kcp-plugin for each release tag.

However, in the Packages for syncer, the tag for the image been override whenever there is a new commit been merged to the main branch.

In the end, it's difficult to figure it out whether the tag of the syncer is correct or not.

Steps To Reproduce

1. Go to Release, take v0.10.0 as an example.
2. You can find the correct binary files for kcp and kubernetes-kcp-plugins
3. Go to Packages for syncer
4. You're not able to find the correct version of the tag associate to kcp with v0.10.0

Expected Behaviour

I'm expecting the Installation section in the Packages should respect to the tag in releases

Additional Context

No response

[kcp-ci-bot]

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kcp-ci-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kcp-ci-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kcp-ci-bot]

@kcp-ci-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.