Correct approach for running a binary as part of a rule which needs to invoke go down the line

I have encountered a situation, whereupon a codegen app, running from a bazel rule, wants to invoke "golang.org/x/tools/imports".Process. This seems to be pretty reasonable; unfortunately `Process` wants to invoke a `go` command somewhere inside it.

Go would not resolve executables via relative paths, so simply conjuring a dirty "PATH" out of "GOROOT" is not an option. I can hackishly obtain an absolute path out of relative GOROOT value, export that in my own simple wrapper and go from there.

However, should not there be some sort of standard way to do such things?

Code generation is increasingly important topic, and thus there's more need to write custom code generator tooling which may need to invoke bits and pieces of the toolchain.

The issue does not name files or tests. Start by tracing the Bazel rule and code-generation entry point that invokes golang.org/x/tools/imports.Process, then examine how GOROOT, PATH, and the go executable are exposed; done means documenting or establishing a standard supported approach for this toolchain invocation.

Written by the indexing model from the issue text.