SqlSetup: Integration tests for SQL Server 2016 and SQL Server 2017 should use the same test config- and script file

[johlju]

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

The integration tests for SqlSetup is run in two jobs, one job for SQL Server 2016 and another job for SQL Server 2017. To simplify coding during the PR #1103 the integration test script file and config file was copied and split into two integration script- and config files.
These should be concatenated so that SQL Server 2016 and SQL Server 2017 (and future versions like SQL Server 2019) is tested in the same integration test script- and config file.

Verbose logs showing the problem

n/a

Suggested solution to the issue

n/a

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