Use upstream definitions, fix gopackagesdriver

[rv32ima]

What type of PR is this?

Bug fix
Feature

What does this PR do? Why is it needed?

With some recent changes made, the gopackagesdriver seems to fail to resolve all standard library imports. This fixes that, as well as migrating the driver to use the upstream definitions as defined here: https://pkg.go.dev/golang.org/x/tools/go/packages#hdr-The_driver_protocol.

Which issues(s) does this PR fix?

Fixes #4184
Fixes #3962

[rv32ima]

It looks like this CI failure: https://buildkite.com/bazel/rules-go-golang/builds/7281#019373f5-722b-4160-8e7b-4cdc32943756 is unrelated to this PR. Going to ignore it for now.

[fmeum]

Cc @JamyDev

[aran]

What else would be needed here to get this landed?

[rv32ima]

@aran

What else would be needed here to get this landed?

I'm not sure. At @devzero-inc, we use this patch-set daily, and I know that it definitively works for us, but we also have an entirely cgo-free code base. Earlier, at @fmeum's request, I tried to dig into /why/ specifically CompiledGoFiles isn't getting populated, and experimented with passing -compiled=true to go list... and, well, that compiles basically every single cgo file in the standard library from scratch, invoking the C compiler a bunch of times... and pinning CPU at 100% for 10+ minutes. Not ideal, especially for something that's invoked quite frequently from the IDE. I'm happy to make any more changes as needed, but I haven't necessarily received anything actionable.

[rv32ima]

@JamyDev addressed your comments

[JamyDev]

@ellie-idb can you update the description to indicate that this is ready for merging in yet, and see if you can fix the build failures?

[rv32ima]

sure, sorry for the delay

[rv32ima]

@JamyDev build failures are fixed

[fmeum]

Could you rebase onto master? GitHub doesn't let me merge this as is.

[rv32ima]

rebased