Replace npm with pnpm (#136)

## Summary

[`pnpm`](https://pnpm.io/) vs `npm`
- Pros
  - Integrated (interactive) version manager
    - `pnpm up-deps` / (aliased `pnpm update -r -i --latest`)
- `npm outdated` / `npm update --save-dev --save` only adhere to
`package.json` semver
- Must manually modify versions for major versions (ex. Vite 5 => 6)
- Can use [`npx
npm-check-updates`](https://github.com/raineorshine/npm-check-updates)
package to provide similar functionality
  - Efficient Disk space
  - Workspace support
- npm added
[support](https://docs.npmjs.com/cli/v8/using-npm/workspaces) but not
aware of any major projects using it
  - Typically [faster installs](https://pnpm.io/benchmarks) than npm
  - Slightly better developer ergonomics (`pnpm dev` vs `npm run dev`)
- [Used](https://pnpm.io/users) by many large projects/companies (Vite,
Svelte, etc)
- Cons
  - Additional install (`npm` included with Node.js)
- Synk
[support](https://docs.snyk.io/supported-languages-package-managers-and-frameworks/javascript/javascript-for-open-source?_gl=1*1gi9low*_gcl_au*MTA2ODIxOTcxNy4xNzM0Mzg4MTY2*_ga*MTEzMzg2NzM3NS4xNzM0MDIzMDg5*_ga_X9SH3KP7B4*MTczNDU0MzI4Mi40LjAuMTczNDU0MzI4Mi4wLjAuMA..#pnpm)
is currently in
[preview](https://app.snyk.io/org/varant-zlai/manage/beta-features)
- package version overrides not currently applying with Synk
(configuration, preview status of integration, ...). Likely because snyk
is configured to scan `package-lock.json` (npm) and not `pnpm-lock.yaml`
(pnpm).
([here](https://app.snyk.io/org/varant-zlai/project/f4bdc116-d05b-4937-96b5-b1f9a02872e5))

---


![image](https://github.com/user-attachments/assets/3fff95c6-f100-4083-9463-042b27763d1f)


![image](https://github.com/user-attachments/assets/decb6b45-60d0-40b5-a37a-803dd6deb302)


## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Documentation**
- Updated README files to reflect the use of `pnpm` as the recommended
package manager, including installation instructions and best practices.

- **New Features**
- Transitioned scripts in the project to utilize `pnpm` for various
tasks including development, building, and testing.

- **Configuration**
- Modified Playwright configuration and other build configurations to
use `pnpm` for starting the web server and managing dependencies.

- **Dependency Updates**
- Updated Spark dependency version from `3.5.0` to `3.5.1` and Jackson
version from `2.15.1` to `2.15.2`.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->

---------

Co-authored-by: Sean Lynch <[email protected]>
Co-authored-by: ken-zlai <[email protected]>

Author: 3 people

build.sbt

@@ -240,14 +240,14 @@ lazy val frontend = (project in file("frontend"))
     buildFrontend := {
       println("Installing frontend dependencies...")
       import scala.sys.process._
-      val npmCiResult = Process("npm ci", file("frontend")).!
+      val pnpmCiResult = Process("pnpm install --frozen-lockfile", file("frontend")).!
 
-      if (npmCiResult != 0) {
-        sys.error("npm ci failed!")
+      if (pnpmCiResult != 0) {
+        sys.error("pnpm install failed!")
       }
 
       println("Building frontend...")
-      val buildResult = Process("npm run build", file("frontend")).!
+      val buildResult = Process("pnpm run build", file("frontend")).!
 
       if (buildResult == 0) {
         println("Copying frontend assets to /hub/public...")

docker-init/README.md

@@ -33,7 +33,7 @@ $ docker compose -f docker-init/compose.yaml up
 
 The **backend** is served at: http://localhost:9000
 
-The **frontend** is served at: http://localhost:3000. This serves statically built code - no live dev server. `cd frontend; npm run dev` for a live dev server.
+The **frontend** is served at: http://localhost:3000. This serves statically built code - no live dev server. `cd frontend; pnpm run dev` for a live dev server.
 
 You can also access the parquet anomaly data table. To do so, from another terminal run:
 

frontend/README.md

@@ -7,7 +7,7 @@ The frontend for Chronon.
 ### Prerequisites
 
 - [Node.js](https://nodejs.org/en/) (LTS version recommended)
-- npm (comes with Node.js)
+- [pnpm](https://pnpm.io/installation) - fast and disk space efficient package manager
 
 ### Installation
 
@@ -26,7 +26,7 @@ The frontend for Chronon.
 
 3. Install dependencies:
    ```bash
-   npm install
+   pnpm install
    ```
 
 ### Development
@@ -53,7 +53,7 @@ Done uploading summaries! 🥳
 3. Then, start the development server:
 
 ```bash
-npm run dev
+pnpm dev
 ```
 
 This will start a local server. The app will automatically reload if you make changes to the code.
@@ -63,7 +63,7 @@ This will start a local server. The app will automatically reload if you make ch
 To create an optimized production build:
 
 ```bash
-npm run build
+pnpm build
 ```
 
 This will create an optimized version of your project in the `build` directory.
@@ -73,7 +73,7 @@ This will create an optimized version of your project in the `build` directory.
 To preview the production build locally:
 
 ```bash
-npm run preview
+pnpm preview
 ```
 
 ### Running Tests
@@ -85,72 +85,72 @@ npm run preview
 To run both unit and integration tests together:
 
 ```bash
-npm run test
+pnpm test
 ```
 
 #### Unit Tests
 
 To run unit tests using Vitest:
 
 ```bash
-npm run test:unit
+pnpm test:unit
 ```
 
 To run unit tests once:
 
 ```bash
-npm run test:unit:once
+pnpm test:unit:once
 ```
 
 #### Integration Tests
 
 To run integration tests using Playwright:
 
 ```bash
-npm run test:integration
+pnpm test:integration
 ```
 
 To run integration tests once:
 
 ```bash
-npm run test:integration:once
+pnpm test:integration:once
 ```
 
 For the Playwright UI to explore test results:
 
 ```bash
-npm run test:integration:ui
+pnpm test:integration:ui
 ```
 
 ### Linting and Formatting
 
 To check code formatting and linting issues:
 
 ```bash
-npm run lint
+pnpm lint
 ```
 
 To format the codebase:
 
 ```bash
-npm run format
+pnpm format
 ```
 
 ### Type Checking
 
 To check the TypeScript types:
 
 ```bash
-npm run check
+pnpm check
 ```
 
 To continuously check types while developing:
 
 ```bash
-npm run check:watch
+pnpm check:watch
 ```
 
 ## Best Practices
 
-1. **Code Style**: This project uses Prettier and ESLint for code formatting and linting. Please run `npm run lint` and `npm run format` before committing changes.
+1. **Code Style**: This project uses Prettier and ESLint for code formatting and linting. Please run `pnpm lint` and `pnpm format` before committing changes.
 2. **Testing**: Ensure all changes are covered with unit and integration tests. Use Vitest for unit tests and Playwright for integration tests.