SqlServerDsc: Add a new pipeline job to test SQL Server Reporting Services 2017, 2019 (and onwards)

[SphenicPaul]

Details of the scenario you tried and the problem that is occurring

Suggestion to add another Azure Pipelines "job" within the build for the SqlServerDsc module to test the SQL Server Reporting Services resources seperately to the existing "jobs" that test the other resources. SQL Server Reporting Services (from SQL Server 2017) onwards is more independent of the other SQL Server resources within this module (since SQL 2017) so this may make more sense.

SQL Server Reporting Services is also not installed (and not tested) as part of SQL Server 2019, integration test and installation methods/EXEs may need to be updated/amended to support testing of later versions of SQL Server Reporting Services (current EXE is from October 2017). See PR #1676 conversations when SQL Server 2019, integration tests were added (but not for SSRS).

Verbose logs showing the problem

n/a

Suggested solution to the issue

Add a new job to azure-pipelines.yml and update/add integration tests (and possibly unit tests) to include integration tests specific to SQL Server Reporting Services from 2017 onwards.

The DSC configuration that is used to reproduce the issue (as detailed as possible)

n/a

SQL Server edition and version the target node is running

n/a

SQL Server PowerShell modules present on the target node

n/a

The operating system the target node is running

n/a

Version and build of PowerShell the target node is running

n/a

Version of the DSC module that was used ('dev' if using current dev branch)

Dev