nogo: instantiate type info for generic types when running under Go >=1.18

[farhaven]

This mirrors what golang.org/x/tools/go/packages does when loading packages.

Should fix #3211 (and probably #3164 as well).

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

This PR adds an initialization that is required for the package loader in nogo to load instantiation information for generic types. This takes a lot of inspiration from what the package loader in golang.org/x/tools does.

Which issues(s) does this PR fix?

Fixes #3211 and #3164

Other notes for review

My company signed the CLA, but it looks like that fact has to percolate through something at Google.

[sluongng]

@fmeum @achew22 @linzhp I don't think we need to stay compatible with Go 1.17 and below in rules_go? There are some precedent such as #3157 where we shipped features exclusively for 1.18

[farhaven]

I've added a test that's failing for two reasons:

• the Go toolchain version needs to be bumped to >= 1.18. I think there's already a PR for that: Update Go to 1.18.3 #3179. That means that this PR will have to wait until Update Go to 1.18.3 #3179 has been merged. Fine with me :)
• org_golang_x_tools needs to be updated to something >= v0.1.11, but I don't have (and don't want) the permission to upload packages to mirror.bazel.build. Update Go to 1.18.3 #3179 also seems to indicate that this would depend on a Gazelle release, so this would also be blocked by that.

[uhthomas]

Should the version of x/tools also be updated in this PR? Feels like it would be required for generics?

[sluongng]

created bazel-contrib/bazel-gazelle#1283 to request for a newer Gazelle release

[linzhp]

Gazelle 0.26.0 was released

[sluongng]

d6138e4 was merged.
I suggest rebase this PR on top of latest origin/master so CI can retry.

[farhaven]

d6138e4 was merged. I suggest rebase this PR on top of latest origin/master so CI can retry.

Thanks for the patience, I was on vacation last week and only just got around to rebasing. Let's see how it works.

[farhaven]

I've updated golang.org/x/tools used by the tests to v0.1.11, looks like the test runs now.

I used the --mirror=false flag to releaser when doing the update, so even though mirror.bazel.build is mentioned as an additional source for the dependency, that needn't be true. This doesn't hurt building/testing and such right now, but might break if the github mirror goes away.

[farhaven]

For some reason, Github won't let me re-request a review, but from my perspective, this looks good to go:

• golang.org/x/tools have been updated to v0.1.11
• golang.org/x/mod has been updated to v0.6.2-dev-something (the same version mentioned in tools' go.mod)
• Building and bazel test //... succeed on CI and (when disabling the CGo tests) on my M1 Mac.

[farhaven]

I've applied the suggestions, rebased the patch on master and squashed the commits down to a single commit to make the history a bit cleaner than "Fix this, fix that, oops, forgot the other thing".