chore: pin eslint-config-prettier and eslint-plugin-prettier versions to prevent malicious package installation

[tusharpandey13]

Pin eslint-config-prettier and eslint-plugin-prettier to exact versions to protect against the recent npm phishing attack that compromised these packages. The caret range ^8.8.0 could have installed malicious versions.

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)

🔍 RCA

A phishing campaign compromised npm maintainer credentials, leading to malicious versions of eslint-config-prettier (10.1.6, 10.1.7) and eslint-plugin-prettier (4.2.2, 4.2.3) being published. Our semver range ^10.0.1 was vulnerable to installing the malicious 10.1.6 and 10.1.7 versions.

📋 Changes

Pin exact versions of potentially vulnerable packages to prevent automatic installation of compromised versions through semver ranges.

• Changed package.json: pinned eslint-config-prettier from ^8.8.0 to 8.8.0 and eslint-plugin-prettier from ^4.2.1 to 4.2.1
• Changed package-lock.json: removed version ranges.

📎 References

https://socket.dev/blog/npm-phishing-campaign-leads-to-prettier-tooling-packages-compromise

🎯 Testing

Automated:
No new tests required - this is a dependency version change with no functional impact.

Manual:

1. Run pnpm install to verify no version conflicts
2. Run pnpm run lint to confirm ESLint configuration still works
3. Verify the pinned versions match the existing pnpm-lock.yaml entries

[developerkunal]

LGTM