workflows: Bump python version on Windows to try to fix lldb failure

[thieta]

I thought the required version is much less than 3.10? Why is this helping / failing?

[tstellar]

In D142719#4085597, @thieta wrote:

I thought the required version is much less than 3.10? Why is this helping / failing?

There is some problem with the environment in the Windows builders where CMake always wants to select the x86 version of the python libraries instead of the x86_64 version. Setting the python-version to the highest supported version on the Windows builders seems to fix this.

[thieta]

In D142719#4085605, @tstellar wrote:

In D142719#4085597, @thieta wrote:

I thought the required version is much less than 3.10? Why is this helping / failing?

There is some problem with the environment in the Windows builders where CMake always wants to select the x86 version of the python libraries instead of the x86_64 version. Setting the python-version to the highest supported version on the Windows builders seems to fix this.

That's curious... No need to block this on figuring it out. So let's merge this at least.

.github/workflows/llvm-project-tests.yml

steps:
           arch: amd64
       # On Windows, starting with win19/20220814.1, cmake choose the 32-bit
       # python3.10.6 libraries instead of the 64-bit libraries when building
       # lldb.  Using this setup-python action to make 3.10 the default
       # python fixes this.
       - name: Setup Python
         uses: actions/setup-python@v4
         with:
-          python-version: '3.10'
+          python-version: '3.11'
       - name: Install Ninja
         uses: llvm/actions/install-ninja@main
       # actions/checkout deletes any existing files in the new git directory,
       # so this needs to either run before ccache-action or it has to use
       # clean: false.
       - uses: actions/checkout@v3
         with:
           fetch-depth: 250