Package differences and changes when setting up PW dev environment

[oliverfanderson]

Several conda packages changed between the Intel and the M4 Mac chip. I believe we should create a separate environment_m4.yml file for the M4 conda dependencies. It seems to work when you delete the specific hash for packages that have issues during installation.

Additionally, there seems to be a newer version of NPM available but our system relies on the older version:

npm notice 
npm notice New major version of npm available! 9.8.0 -> 11.5.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.5.2
npm notice Run npm install -g npm@11.5.2 to update!
npm notice 

After running the command, we get this output:

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@11.5.2
npm ERR! notsup Not compatible with your version of node/npm: npm@11.5.2
npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"}
npm ERR! notsup Actual:   {"npm":"9.8.0","node":"v20.5.1"}

npm ERR! A complete log of this run can be found in: /Users/oliverfanderson/.npm/_logs/2025-08-14T19_50_55_514Z-debug-0.log

When running npm audit fix in the client directory we get this output:

# npm audit report

esbuild  <=0.24.2
Severity: moderate
esbuild enables any website to send any requests to the development server and read the response - https://github.com/advisories/GHSA-67mh-4wv8-2f99
fix available via `npm audit fix --force`
Will install vite@7.1.2, which is a breaking change
node_modules/esbuild
  vite  0.11.0 - 6.1.6
  Depends on vulnerable versions of esbuild
  node_modules/vite

2 moderate severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force