ci(release): fix publishing krew plugin; add '.exe' extension to Windows binary

[HollowMan6]

Overview

Fix publishing krew plugin in release CI

There's an error that stops it from getting the right tag, which is, a needs: retag is needed so that it can get the value from ${{ needs.retag.outputs.NEW_TAG }}:

However, fixing that won't work still: https://github.com/HollowMan6/kubescape/actions/runs/4392160217/jobs/7691893332
As you can't override the GITHUB_REF variable due to GitHub Actions' limit, quoting from the GitHub Actions' documentation: "If you attempt to override the value of one of these default variables, the assignment is ignored."

So I moved the Publish Krew plugin into a separate CI, which is triggered by exactly matching the tag created by the release CI. Also as events triggered by the GITHUB_TOKEN will not create a new workflow run, I changed the release token into the secrets.GH_PERSONAL_ACCESS_TOKEN.

Test in my fork:
https://github.com/HollowMan6/kubescape/actions/runs/4392626675 results in PR: kubernetes-sigs/krew-index#3000

Then I fixed the if: check so that it won't get triggered in a fork.

add '.exe' extension to Windows binary

Add '.exe' extension to Windows binaries, as Windows executables usually have .exe extension.

[HollowMan6]

Just revert adding the '.exe' to the release binary, as that naming convention was introduced long time ago and it looks like it would break a lot of things if we introduce this change: https://github.com/search?q=kubescape-windows-latest&type=code

However, I would still recommend adding the '.exe' to the binary inside the tarball, as so far that is only used for Krew and there's still chance for it to get corrected. https://github.com/search?q=kubescape-windows-latest.tar.gz&type=code

[matthyx]

@dwertent fine for me