Go extraction reconciliation: Ensure backwards compatibility for multi-language builds

[henrymercer]

Additionally autobuild Go in the autobuild Action to ensure backwards compatibility for users performing a multi-language build within a single job. For example, consider a user with the following workflow file:

- uses: github/codeql-action/init@v2
  with:
    languages: go, java
- uses: github/codeql-action/autobuild@v2
- uses: github/codeql-action/analyze@v2

• With Go extraction disabled, we will run the Java autobuilder in the autobuild Action, ensuring we extract both Java and Go code.
• With Go extraction enabled, taking the previous behavior we'd run the Go autobuilder, since Go is first on the list of languages. We wouldn't run the Java autobuilder at all and so we'd only extract Go code.

We therefore introduce a special case here such that we'll autobuild Go in addition to the primary non-Go traced language in the autobuild Action. This special case behavior should be removed as part of the next major version of the CodeQL Action.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.

[angelapwen]

Overall this makes sense to me. Seems unavoidable if we want to maintain full backwards compatibility. Happy to re-review/approve when out of draft mode.

[angelapwen]

Looks good to me! Approving for now, but I believe we are waiting until the latest release to go in before merging.