Migrate AzDO pipelines to azdo-pipelines v2 .config model

[Copilot]

This updates the repo from legacy .azure-pipelines definitions to the current azdo-pipelines v2 pattern used across Azure Tools repos, aligned with the referenced migration PRs and guide. It preserves the existing CI/release intent while switching to the new shared template model.

• Pipeline definitions moved to .config and upgraded

  • Renamed .azure-pipelines/1esmain.yml → .config/build.yml
  • Added .config/release.yml (replacing legacy release pipeline)
  • Switched template references to azdo-pipelines/1es-mb-main.yml and azdo-pipelines/1es-mb-release-extension.yml
  • Updated template repo ref to azext-pt/v1
  • Adopted shared variables from azdo-pipelines/azcode.variables.yml

• Reviewer-required wiring from reference migration applied

  • Added npmFeed parameter wiring in both build and release pipelines
  • Release pipeline now uses shared release variables:
    • releaseServiceConnection: ${{ variables.extensionReleaseServiceConnection }}
    • releaseApprovalEnvironment: ${{ variables.extensionReleaseApprovalEnvironment }}
  • Set release package target explicitly:
    • packageToPublish: vscode-node-azure-pack

• Legacy/obsolete pipeline assets removed

  • Deleted:
    • .azure-pipelines/release.yml
    • .azure-pipelines/SignExtension.signproj
    • .azure-pipelines/compliance/CredScanSuppressions.json
    • .azure-pipelines/compliance/PoliCheckExclusions.xml
  • Moved compliance config:
    • .azure-pipelines/compliance/tsaoptions.json → .config/tsaoptions.json

• Packaging ignore updated for new layout

  • .vscodeignore now excludes .config/** instead of .azure-pipelines/**

Example of the new release-template wiring:

extends:
  template: azdo-pipelines/1es-mb-release-extension.yml@azExtTemplates
  parameters:
    packageToPublish: vscode-node-azure-pack
    publishVersion: ${{ parameters.publishVersion }}
    dryRun: ${{ parameters.dryRun }}
    releaseServiceConnection: ${{ variables.extensionReleaseServiceConnection }}
    releaseApprovalEnvironment: ${{ variables.extensionReleaseApprovalEnvironment }}
    npmFeed: ${{ variables.npmFeed }}

Original prompt

Migrate this repository to the new Azure DevOps pipelines model in the same pattern used by the following reference PRs:

• Try out the new pipelines vscode-containers#365
• Use internal NPM feeds vscode-containers#471
• Migrate Azure DevOps CI/release pipelines to azdo-pipelines v2 (.config model) vscode-azureresourcegroups#1447
• Migration guide: https://github.com/microsoft/vscode-azuretools/blob/main/azdo-pipelines/MIGRATION.md
• Background/README: https://github.com/microsoft/vscode-azuretools/blob/main/azdo-pipelines/README.md

IMPORTANT — before writing any code:

1. Read through ALL review comments and discussion on Migrate Azure DevOps CI/release pipelines to azdo-pipelines v2 (.config model) vscode-azureresourcegroups#1447. That PR may contain reviewer feedback identifying mistakes or required corrections. Do not repeat those mistakes in this PR.
2. The vscode-azureresourcegroups PR (#1447) may also include additional changes beyond the vscode-containers reference PRs. Evaluate whether those additional changes are applicable to this repository and apply them if so.

IMPORTANT — before making any changes:
3. Check whether this repository contains the existing pipeline files that are meant to be migrated (e.g. the AzDO pipeline YAML files referenced in the migration guide). If one or both pipeline files are missing from this repository, do NOT create them. Instead, close this PR without merging and leave a comment explaining which files were absent.

Scope and expectations (only if pipeline files exist):

1. Identify and migrate existing pipeline definitions/templates in this repo to the new azdo-pipelines approach.
2. Apply equivalent structural changes seen in the reference PRs, adapted for this repository.
3. Update any supporting config/docs in-repo that must change due to the pipeline migration.
4. Preserve existing behavior and release/CI intent.
5. Validate by running the repo's relevant checks/tests where feasible in the agent environment.
6. In the PR description, summarize what changed, note any intentional deviations from the reference PRs, and include a brief validation summary.

Constraints:

• Keep changes focused on pipeline migration and directly related follow-up edits.
• Avoid unrelated refactors.
• Ensure YAML and template references are consistent and non-breaking.