Addresses #394, #409, adding SSRS 2022 vNext support to the SQLServer…

[mhallockPcty]

…Version enum

Fixes #394 #409 .

Changes proposed in this pull request:

• Adds SSRS 2022 as vNext in SQLServerVersion enum to allow operations on SSRS 2022

How to test this code:

• Try using "16" as SQL server version in various commands

Has been tested on (remove any that don't apply):

• Powershell 3 and above
• Windows 7 and above
• SQL Server 2012 and above

[mhallockPcty]

So, Im happy to attempt to blindly fix this... it looks like your build is downloading SQL Server 2017 files, and is hard coded to use SQLServervNext in all the build steps, which is gonna change as this is updated again and again... It looks like the last time you guys did this (478edd5) this was just changing the version numbers on the downloads / temp / sql powershell module locations... I couldn't discern where you were downloading from to see if a SQLServer2022-x64-ENU.exe and SQLServer2022-x64-ENU.box existed at that location (thus the "blind attempt").

The PowerBI downloads throw me though, those don't look versioned and I have no experience with it to know if I can just update this or not. Please advise.

Also I believe 2017 is where you guys decoupled SSRS from SQL installs, so maybe that's why this hasn't been done yet? We'd need to rebuild your build pipeline to handle that split?

[mhallockPcty]

@microsoft-github-policy-service agree

[Petebro-MSFT]

Remove SQLServervNext, we added that when SQL 2019 was announced but without a release date or branding.

[mhallockPcty]

Removed. Note the build is still failing with an error that looks intermittent on your builds? I see previous builds failing with the same issue that it looks like someone just kept hitting the retry button on until it worked... hopefully that's all my failure is?

[Petebro-MSFT]

I’ll investigate the build issues as well.

[Petebro-MSFT]

One small change needed