feat: Merge cps-v2-dev in v1-DEV

[Shreyas-Microsoft]

Purpose

This pull request introduces several improvements to the CI/CD pipeline and development environment, focusing on expanding Docker image build/push capabilities, updating workflow logic, and modernizing the dev container setup. The changes enhance automation, support for new branches, and toolchain consistency.

CI/CD Pipeline Enhancements:

• Expanded Branch Support and Tagging

  • The Docker image build workflow (build-docker-image.yml) now supports the psl-docker-build-and-push-v2 and psl-cps-v2 branches for both push and pull request triggers. Images built from these branches are tagged as latest_v2 for consistency. [1] [2] [3] [4]
  • The workflow conditions for Azure login, ACR login, and image push now include these new branches, ensuring CI/CD runs as expected for feature development. [1] [2] [3] [4]

• New Docker Image Build

  • Added a build-and-push step for the ContentProcessorWorkflow Docker image, aligning it with the other services.

Dev Container and Toolchain Updates:

• Switch to pnpm and Corepack

  • The dev container now uses pnpm (enabled and prepared via Corepack) instead of yarn for installing dependencies in ContentProcessorWeb, promoting faster and more reliable installs. [1] [2]
  • Global NPM tools are updated, and yarn is no longer installed by default.

• Python Symlink for Compatibility

  • A symlink from /usr/bin/python to /usr/bin/python3 is created to improve compatibility with tooling expecting python.

• Cleanup and Permissions

  • The dev setup script no longer attempts to chmod register_schema.sh (which is now a Python script and cross-platform).

Workflow Logic and Permissions Adjustments:

• Workflow File and Input Cleanup

  • The deploy workflow file is renamed from deploy-v2.yml to deploy-linux.yml, and the runner OS input logic is removed in favor of always using ubuntu-latest, simplifying the workflow and reducing unnecessary complexity. [1] [2] [3] [4] [5] [6] [7]

• Permissions and Conditional Logic

  • Permissions are explicitly set in deploy-orchestrator.yml, and the cleanup step is now only triggered if the deployment succeeded, preventing resource cleanup in failed runs. [1] [2]

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information