rules_go 0.40+ broke gopls resolving stdlib imports in VS code

### What version of rules_go are you using?

Tested with 0.40.1 and 0.42

### What version of gazelle are you using?

0.31.1 and 0.33

### What version of Bazel are you using?

6.4.0

### Does this issue reproduce with the latest releases of all the above?

Yes

### What operating system and processor architecture are you using?

Linux amd64

### Any other potentially useful information about your toolchain?

Tested with gopls 0.13.2 and 0.14.1.

Using these settings in VS code:

```json
"go.goroot": "${workspaceFolder}/bazel-${workspaceFolderBasename}/external/go_sdk/",
"go.toolsEnvVars": {
"GOPROXY": "off",
"GOPACKAGESDRIVER": "${workspaceFolder}/scripts/gopackagesdriver.sh",
},
"gopls": {
"build.directoryFilters": [
"-bazel-bin",
"-bazel-out",
"-bazel-testlogs",
"-bazel-${workspaceFolderBasename}"
],
[...]
},
```

and this `gopackagesdriver.sh`:

```shell
#!/bin/sh

bazel="$(command -v bazel || command -v bazelisk)"
# reset GOPROXY to default
unset GOPROXY

# don't fetch internal stuff
export GOPRIVATE="[...]*"

exec "${bazel}" run -- @io_bazel_rules_go//go/tools/gopackagesdriver "$@"
```

### What did you do?

Updated rules_go from 0.39.1 to 0.42 (and then later backtracked the problem to 0.40)

### What did you expect to see?

gopls is able to resolve stdlib imports in VS code as before.

### What did you see instead?

A lot of import errors in the format of `could not import $PKG (cannot find packge "$PKG" in GOROOT or GOPATH)`.

Reproduce the issue with the listed rules_go, Gazelle, Bazel, gopls, and VS Code versions using scripts/gopackagesdriver.sh and the @io_bazel_rules_go//go/tools/gopackagesdriver entry point. Compare behavior between rules_go 0.39.1 and 0.40+; done means gopls resolves standard-library imports without the reported GOROOT or GOPATH errors.

Written by the indexing model from the issue text.