Update build pipeline to use VS2019

[networkfusion]

Description

CICD currently uses VS2017. VS2019 will be required in future, so we should update if possible

Motivation and Context

Ensures that we dont get caught out by azure-pipelines removing VS2017 as a valid image.

• Resolves Update CICD pipelines of all libs to use VS2019 Home#667

How Has This Been Tested?

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[nfbot]

Hi @networkfusion,

😞 If this PR does address any issue, you have to remove the content Fixes/Closes/Resolves(...) under 'Motivation and Context'

[nfbot]

Hi @networkfusion,

🤔 All our issues are tracked in Home repo. If this PR addresses an issue that's mentioned there, please make sure it references it using the correct pattern: nanoFramework/Home#NNNN.