ci: use npm ci for deterministic installs

[cb-karthikp]

Use npm ci for deterministic dependency installation in the Makefile install target and the prepack script.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues
✅	Secrets	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: e9f1aa3d-a4e4-4ec5-b855-d4bb4ab8d00f

📥 Commits

Reviewing files that changed from the base of the PR and between b74a74e and 39a16b5.

📒 Files selected for processing (2)

• Makefile
• package.json

---

Walkthrough

The installation and packaging workflows now use npm ci instead of npm install.

Changes

Deterministic npm installation

Layer / File(s)	Summary
Update installation workflows Makefile, package.json	The install target and prepack script now run npm ci.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 39a16

This PR makes CI installs more deterministic without any identified merge-blocking risk; it is merge-ready after normal checks and review.

Suggested reviewers: cb-alish

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

_{Comment @coderabbitai help to get the list of available commands.}