Make PTVS build for Dev18

[StellaHuang95]

• Update Source Code Build Configuration for Dev18

  • Build Configuration Files
  • C++ Project Files (vcxproj files)
  • C# Project Files (.csproj files)
  • Package Configuration
  • Assembly Version Files
  • VSIX Manifest

• Build Pipelines: Update azure-pipelines.yml, release, and compliance pipeline configurations.

  The current build pipeline uses the MSBuild@1 Azure task, which doesn't yet support Dev18. While the MSBuild command-line tool already supports Dev18 builds, we're waiting for Azure Pipeline task support.

  Track progress at [enhancement]: Please add support for VS 2026 (18.0) - MSBuild & Vs build Task azure-pipelines-tasks#21319

• Update VS Bootstrapper Configuration

  The build pipeline currently generates a Dev17 Visual Studio installer with the latest PTVS changes for testing purposes. This needs to be updated for Dev18.

  • Update create_vs_bootstrapper.yml
  • Coordinate with CTI: Notify the team that the bootstrapper will now generate Dev18 installer bits instead of Dev17

• Snap PTVS Main to Dev17 Release Branch

  • Create branch protection rules for the release branch

  Currently, all changes flowing into Visual Studio main are targeting Dev18. Since the VS team has already snapped their main branch to the Dev17 release branch, we should also create a clear separation between Dev17 and Dev18 development streams.

  This maintains stable Dev17 releases and also enables parallel Dev18 development.

• Update the Build and Debug Instructions for PTVS: https://github.com/microsoft/PTVS/wiki/Build-and-Debug-Instructions-for-PTVS

• Address Dev18-Specific Issues

  • https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2416924
  • Cannot locate performance tools when launching python profiling #8276
  • Test Result didn't show after executing in TE #8277
  • The option "Python/Native Debugging" is missing. #8290
  • The button that can quickly start LiveShare is missing. #8291

[rizi]

Stella Huang (@StellaHuang95) wouldn't it make sense that the tasks just use the latest installed version of VS/MsBuild?
At the moment the tasks needs to be updated to support new version of VS.
Also within the tasks "use latest version" is quite misleading, because it means the latest version of VS that is supported by the task and not the latest installed version