Fix CI jobs that broke as a result of windows-latest being upgraded to Windows Server 2022

[henrymercer]

windows-latest is currently migrating from an image based on Windows Server 2019 to an image based on Windows Server 2022. This breaks some of our CI jobs for two reasons:

1. Build tracing doesn't yet support Windows Server 2022
2. Python 2 isn't supported in the windows-2022 image.

This PR addresses (1) by moving relevant jobs to use the windows-2019 image and (2) by fixing a typo that prevented setup-python from downloading and installing Python 2 when it's not already in the Actions VM image.

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.

[henrymercer]

@github/codeql-action-reviewers Since this PR changes a few jobs from windows-latest to windows-2019, we'll need to modify the required checks before we merge this.

[aeisenberg]

This will probably affect some customers who are on windows-latest. We should probably add a change log entry for this. Or maybe even in the readme.

Yeah...this line needs to change, or at least add a caveat:

codeql-action/README.md

Line 42 in a57642e

# CodeQL runs on ubuntu-latest, windows-latest, and macos-latest

[henrymercer]

I thought we'd already done a changelog note for Windows Server 2022, but seemingly we only did one for the CLI. I agree we should do a changelog and update the readme, but I suggest we do so in a separate PR so we can get the checks fixed on main and unblock other PRs.

[aeisenberg]

That's fine by me. A changelog note as well as making a note in the README in a separate PR. Thanks for getting this done.

[henrymercer]

Required checks updated.