PR Summary

This pull request includes several changes across multiple pipeline templates to streamline the use of .NET Core SDK and improve the bootstrap process. The most important changes involve replacingStart-PSBootstrap withUseDotNet@2 tasks and updating theStart-PSBootstrap command to use the-Scenario parameter.

Streamlining the use of .NET Core SDK:

• .pipelines/templates/compliance/apiscan.yml: ReplacedStart-PSBootstrap withUseDotNet@2 task for using the .NET Core SDK.
• .pipelines/templates/linux.yml: AddedUseDotNet@2 task for using the .NET Core SDK.[1][2]
• .pipelines/templates/nupkg.yml: AddedUseDotNet@2 task and removedStart-PSBootstrap.
• .pipelines/templates/release-validate-fxdpackages.yml: ReplacedStart-PSBootstrap withUseDotNet@2 task for using the .NET Core SDK.
• .pipelines/templates/testartifacts.yml: ReplacedStart-PSBootstrap withUseDotNet@2 task for using the .NET Core SDK.[1][2]

UpdatingStart-PSBootstrap command:

• .pipelines/templates/linux-package-build.yml: UpdatedStart-PSBootstrap to use-Scenario Package.
• .pipelines/templates/mac-package-build.yml: UpdatedStart-PSBootstrap to use-Scenario Package.
• .pipelines/templates/windows-hosted-build.yml: UpdatedStart-PSBootstrap to use-Scenario Package and removed redundant calls.[1][2][3][4]
• .pipelines/templates/windows-package-build.yml: UpdatedStart-PSBootstrap to use-Scenario Package.[1][2]
• .vsts-ci/linux/templates/packaging.yml: UpdatedStart-PSBootstrap to use-Scenario Package.

These changes aim to standardize the usage of .NET Core SDK and improve the maintainability of the pipeline scripts.

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all.h,.cpp,.cs,.ps1 and.psm1 files have the correct copyright header
• This PR is ready to merge and is notWork in Progress.
  • If the PR is work in progress, please add the prefixWIP: or[ WIP ] to the beginning of the title (theWIP bot will keep its status check atPending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    - [ ] Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact onPowerShell Editor Services which is used in thePowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact onPSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact onEditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: