ci/windows: use the vs backend instead of ninja backend

So we have some coverage of that.

Signed-off-by: Ran Benita <ran@unusedvar.com>

.github/workflows/windows.yml

@@ -25,18 +25,14 @@ jobs:
         shell: powershell
         run: |
           python -m pip install --upgrade meson
-          Invoke-WebRequest -Uri https://github.com/ninja-build/ninja/releases/download/v1.10.1/ninja-win.zip -OutFile ninja.zip
           Invoke-WebRequest -Uri https://github.com/lexxmark/winflexbison/releases/download/v2.5.23/win_flex_bison-2.5.23.zip -OutFile win_flex_bison.zip
           Expand-Archive -Path win_flex_bison.zip -DestinationPath bin
-          Expand-Archive -Path ninja.zip -DestinationPath bin
           Write-Output ((Get-Location).ToString() + "./bin") | Out-File -Append -FilePath $env:GITHUB_PATH -Encoding utf8
       - name: Setup
         shell: cmd
         run: |
           call "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x64
-          meson setup -Denable-wayland=false -Denable-x11=false -Denable-docs=false -Denable-xkbregistry=false build
-        env:
-          CC: cl
+          meson setup --backend=vs -Denable-wayland=false -Denable-x11=false -Denable-docs=false -Denable-xkbregistry=false build
       - name: Build
         shell: cmd
         run: |