[ci]: Complete sonic-swss CI-unification cutover

[theasianpianist]

Summary

Complete all migration changes owned by the sonic-swss repository in one PR,
following merged sonic-swss-common #1222 and sonic-sairedis #2016.

This PR moves SWSS Build and VS-test host setup to the shared
sonic-swss-common/ci/buildenv_setup mechanism, makes sonic-swss the single
owner of the reusable docker-sonic-vs build and VS-test templates, and cuts
SWSS's own BuildDocker/Test stages over to those templates.

azure-pipelines-dash.yml is deprecated and intentionally unchanged.
Cross-repo references from sonic-swss-common/sonic-sairedis and the final
required shared-infra gate remain separate follow-ups because they modify other
repositories/policy.

Build and local development

• Add declarative build-env/packages/{base,tooling,test}.yaml and
  build-env/upstream-artifacts.yaml.
• Declare only immediate Build artifacts (sonic-sairedis + dash-api); the
  sairedis artifact recursively supplies swss-common/common-libs/VPP and shared
  package/post-install configuration.
• Replace inline apt/artifact/Redis/VPP setup in the complete Build matrix with
  shared buildenv_setup.
• Add canonical build-env/build.sh for package build + Rust tests.
• Delete the hardcoded local build-env/container-setup.py artifact installer.
• Preserve the existing non-root/home-mounted/custom-setup local Docker workflow,
  but drive its canonical dependencies through buildenv_setup.
• Publish build-env/ additively beside the existing top-level DEBs and coverage
  files for future downstream cascading.
• Expose repo + staged_upstreams on the Build template for same-run reuse by
  upstream pipelines.

Shared docker-sonic-vs build

• Replace build-docker-sonic-vs-template.yml with reusable
  build-docker-template.yml.
• Parameterize consumer differences: debug package, VPP, gcov source handling,
  nexthopgroup, and current-run swss-common/sairedis artifacts.
• Keep SWSS's current behavior as the defaults, including ASAN image tagging,
  VPP sysctl handling, coverage-source restoration, branch/result filters, and
  package set.
• Parameterize the swss-owned Dockerfile so sairedis and swss-common can reference
  the same implementation in later PRs.

Shared VS-test execution

• Replace test-docker-sonic-vs-template.yml with reusable
  run-vs-tests-template.yml.
• Use buildenv_setup --scope test plus SWSS-owned packages/test.yaml and
  test-scoped artifact declarations for the Ubuntu 22.04 host.
• Preserve kernel-module setup, Redis configuration, Docker image loading,
  retries/parallelism, JUnit, logs, coverage, ASAN reporting, VRF smoke check,
  and SWSS's single_asic_voq_fs test pass.
• Provide neutral defaults, repo, staged_upstreams, extra_modes, and
  explicit failure-policy parameters for later sairedis/swss-common adoption.

Validation completed before PR

• YAML parsing, shell syntax, Docker Compose config, git diff --check.
• Dockerfile docker build --check.
• buildenv_setup --dry-run for bookworm/trixie across amd64/armhf/arm64 and
  Ubuntu 22.04 Test scope.
• Matrix assertions for conditional package/artifact selection.
• Synthetic end-to-end Build cascade:
  swss -> sairedis -> common-libs/swss-common/sonic-yang/VPP + dash-api,
  including required-staged enforcement, VPP's isolated install environment,
  and shared Redis source resolution.
• Synthetic Test cascade for common-libs, swss-common Ubuntu test-host and
  sonic-buildimage Ubuntu artifacts.
• Real Build setup in sonic-slave-bookworm:master-amd64, using sairedis PR
  artifact 1183201 as a required staged bundle; all nested artifacts and the
  shared Redis hook installed successfully.
• Real Test setup in Ubuntu 22.04; libyang/common-libs, swss-common host DEBs,
  protobuf/dash DEBs, Python libyang binding and Redis setup completed. This run
  caught and fixed the YAML quoting of --force-confask,confnew (d66a8129).
• Independent high-confidence review reported no remaining significant issues.

Temporary CI note

Post-merge sairedis master run 1186981 (source 24673778) is still in
progress. buildenv_setup intentionally resolves only completed upstream runs,
so the first Azure run may select a pre-migration sairedis master artifact that
does not publish build-env/. Once 1186981 completes, Azure CI will be
retriggered and must use the cascade-ready master artifact across bookworm,
arm, and trixie legs.

Design context: sonic-net/SONiC#2419.

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[theasianpianist]

/azp run

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[theasianpianist]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).