fix: Configured Microsoft Package Feed Proxy

[Priyanka2-Microsoft]

Purpose

• ...
  This pull request updates the development environment to ensure all Python and Node.js package installations are routed through the Microsoft Package Feed Proxy. This is essential for compatibility with Microsoft-managed devices, where direct access to public registries may be blocked. The changes affect Dockerfiles, environment variables, configuration files, and documentation to enforce the use of internal package feeds for pip, uv, and npm, and also add timing for npm install steps for better diagnostics.

Package feed proxy enforcement and configuration:

• Added https://packagefeedproxy.microsoft.io/pypi/simple/ as the index URL at the top of all relevant requirements.txt files and in the [tool.uv] section of pyproject.toml to ensure all Python package installations use the Microsoft Package Feed Proxy. [1] [2] [3] [4]
• Added .npmrc with the internal registry URL and updated Dockerfiles, environment variables, and devcontainer.json to route all npm installations through the proxy. [1] [2] [3] [4] [5]
• Updated documentation (LocalDevelopmentSetup.md) to explain the proxy setup and how to override it if needed.

Development container and CI improvements:

• Updated the base image in .devcontainer/Dockerfile to use bookworm and set environment variables for pip, uv, and npm registries. [1] [2]
• Updated devcontainer.json and devcontainer-lock.json to specify the correct node feature configuration and lock down feature versions. [1] [2]

CI pipeline and automation updates:

• Modified all GitHub Actions workflows to use the internal pip index when installing dependencies, ensuring CI jobs also use the proxy. [1] [2] [3] [4]

Build and setup scripts:

• Added timing output for npm install steps in shell and PowerShell scripts, as well as in Dockerfiles, to help diagnose slow installs. [1] [2] [3] [4]

These changes collectively ensure a seamless development and CI experience on Microsoft-managed devices by routing all package installations through the required internal proxies.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

Coverage Report •

File	Stmts	Miss	Cover	Missing
TOTAL	3835	552	85%

report-only-changed-files is enabled. No files were changed during this commit :)

Tests	Skipped	Failures	Errors	Time
837	0 💤	0 ❌	0 🔥	10.298s ⏱️