Add toolchain param to affected actions

[kotlaja]

What type of PR is this?

Other - Migration

What does this PR do? Why is it needed?
It sets go toolchain type inside affected actions. This is part of the migration of Automatic Exec Groups inside Bazel downstream.

Which issues(s) does this PR fix?
Please check bazelbuild/bazel#19981 for additional info.

Other notes for review

[kotlaja]

Hey @fmeum, thanks for helping out here! Also, do you maybe know when will be the next release? I'm interested in when I'll be able to use this change inside rules_cc. Thanks! :)

[fmeum]

We can probably do one this or next week.

Cc @tyler-french

[kotlaja]

Great, thanks! Could you please ping me once it's done so I can bump its version in relevant rules and speed up the AEGs migration? @tyler-french @fmeum

[fmeum]

@kotlaja rules_go 0.43.0 is out now

[kotlaja]

Oh no, there were two more actions which needed this change, I saw now. Sorry. :(
Can you please review #3760?

[anguslees]

For visibility, I think this PR (and the followup #3760) are incomplete. Golang actions need both go and cpp toolchains available - when cgo is enabled. The AEG docs say this needs to be done by declaring a new exec_group that mentions both toolchains, so platform resolution is able to take both into account:

If you need to use multiple toolchains on a single execution platform (an action uses executable or tools from two or more toolchains), you need to manually define exec_groups (check When should I use a custom exec_group? section).

[kotlaja]

Thanks, @anguslees, for catching this! I will take a look next week.

Yes, you're right, when we're using more than 1 toolchain in an action, we must define a custom exec group for it. Ironically, I wrote that documentation you're referring to, used it in other rules, but missed this case with cgo in go rules. Will take another look. Thanks again!