Yes. These tests are for a particular workaround in the CLI and action for indirect tracing of go code. I'm actually not sure what this is. It's something that @mbg implemented. It's testing that if we're using a version of go that supports statically linked binaries, we can still build a database even though the CodeQL go tracer does not support statically linked binaries. If we ever do implement this in the go tracer, then these tests will start to fail.

I moved from a fixed version to default so that we won't need to update these tests again in the future.

We only need to test a single version since this is a mechanism that is in the action, and independent of the codeql version.

Look at the "Deprecating a CodeQL version" section of CONTRIBUTING.md for more information around how this deprecation works.