SqlServerDsc: Add a new pipeline job to test SQL Server 2012 family

[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 2012 family (e.g. SQL Server 2012 and Reporting Services 2012).

Note: Implementing equivalent changes for SQL2014 (#1677) is likely to be a priority change/fix over this one.

Verbose logs showing the problem

n/a

Suggested solution to the issue

Add a new job to azure-pipelines.yml and update integration tests and unit tests to cater for the SQL2012, integration tests, and additional references to SQL Server version (e.g. 11 or 110) as appropriate.

Fix any resource issues that addition of tests for SQL2012 may identify.

See issue #1310 and PR #1676 (for example issue and resolution in respect of SQL2019).

Note: Implementing equivalent changes for SQL2014 (#1677) is likely to be a priority change/fix over this one.

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