Go/Bazel: fix gazelle invocation to use bundled bazel go

[redsun82]

If I recall correctly, we were avoiding using the gazelle rule because of some compilation problem on macOS, which seems to be gone with the current versions of rules_go and/or gazelle.

This will make sure that gazelle uses the bundled go version: prior to this, the build through make was misbehaving if go was not installed.

[criemen]

LGTM!

[mbg]

Happy to sign off on this on behalf of the Go team, but I can't say I have much insight into the effects of these changes. I also don't think I have a way of testing this. It may be worth linking this PR in the issue that prompted this change and ask the user there to test it, to verify that this resolves the problem for them?

[redsun82]

Happy to sign off on this on behalf of the Go team, but I can't say I have much insight into the effects of these changes. I also don't think I have a way of testing this. It may be worth linking this PR in the issue that prompted this change and ask the user there to test it, to verify that this resolves the problem for them?

The way I tested this, is to do bazel clean --expunge from a codeql checkout, remove go from the system (in my case it was brew remove go). This was causing make to fail before this PR, and succeed after it. I will link this PR on the user ticket!