ci: add parallelized pipeline with node_modules caching (#368)

[codemagician1949]

Summary

Reduces CI wall-clock time by parallelizing backend, frontend, and contracts jobs and introducing a node_modules cache keyed on package-lock.json so npm ci is skipped on cache hits.

Changes

• .github/workflows/ci-performance.yml — new parallelized workflow with three concurrent jobs:
  • backend: checkout → restore nm cache → install (if miss) → lint → typecheck → test
  • frontend: checkout → restore nm cache → install (if miss) → build → lint → test
  • contracts: checkout → restore cargo cache → fmt → clippy → test → build WASM
  • node_modules cache key: nm-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
  • Cargo cache key: cargo-${{ runner.os }}-${{ hashFiles('**/Cargo.lock') }}
• .github/workflows/frontend-ci.yml — replaced npm install with npm ci for deterministic, reproducible installs

Why This Helps

Before	After
Jobs run sequentially or in separate workflows without shared caching	All three suites run in parallel
npm install mutates lockfile on frontend	npm ci respects lockfile exactly
No node_modules cache	Cache hit skips install entirely on repeat runs

Closes #368
Closes #369
Closes #370
Closes #360

[vercel]

@Gbangbolaoluwagbemiga is attempting to deploy a commit to the joelpeace48-cell's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@codemagician1949 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits