AppVeyor: move to VS 2022 image

[NickCraver]

The update blog post (https://www.appveyor.com/updates/2023/02/24/) doesn't match the inventory (https://www.appveyor.com/docs/windows-images-software/), primarily: .NET 6 SDK which is LTS is no longer on the 2019 image which seems like an oops. Bypassing the issue for now by getting on the 2022 image.

[mgravell]

6.0.406 exists, but if 6.0.309 works: fine (dammit, you pushed more)

[mgravell]

7.0.200 ? I mean, we can see whether 201 with force works, but...

[NickCraver]

I dunno...this image is a PITA, getting it working with forcing so it doesn't break when they add 6.x back to the image once someone realizes it's missing too...

[slorello89]

@NickCraver - aren't the SDKs given unique package names? choco install dotnet-6.0-sdk / choco install dotnet-7.0-sdk?

[NickCraver]

@slorello89 I was going off https://community.chocolatey.org/packages/dotnet-sdk/7.0.201 - but also swamped in 8 other things atm, if y'all have a good handle here push away on this branch, obviously this is just a stream of failure atm :)

[slorello89]

worth a shot :)

[slorello89]

Lol @NickCraver -

    choco install dotnet-sdk --version 6.0.406 --force
    choco install dotnet-sdk --version 7.0.201 --force

Wasn't being split into two lines so it was running choco install dotnet-sdk --version 6.0.406 --force choco install dotnet-sdk --version 7.0.201 --force - naturally it couldn't find the choco or install packages so. . . fail. I left it with dotnet-6.0-sdk and dotnet-7.0-sdk - which I think are the more correct packages (I'm sure you two have a better idea about who to ask about it - but I think are both officially supported)

[NickCraver]

DAMMIT, thanks Steve :)