chore(deps): resolving package release issues

[Sourav-kashyap]

Description

This PR upgrades project dependencies to their latest versions and resolves issues caused by version mismatches and breaking changes.

Changes

Updated all dependencies and devDependencies to the latest versions
Resolved version conflicts and peer dependency issues

Checklist

• Performed a self-review of my own code
• npm test passes on your machine

[sonarqubecloud]

SonarQube reviewer guide

Summary: Downgrade husky from v9 to v7 and update multiple dependencies to newer versions, including security and compatibility fixes.

Review Focus:

• The husky downgrade from 9.1.7 to 7.0.4 is a significant version change that alters the binary path (bin.js → lib/bin.js) and Node.js requirement (>=18 → >=12). Verify this is intentional and test git hooks functionality.
• Multiple major dependency upgrades: helmet (5→8), express-rate-limit (6→8), rate-limit-memcached (0.6→1.0), rate-limit-redis (3→4), and loopback4-* packages. Ensure compatibility with your codebase and test rate limiting features thoroughly.
• New direct dependency on @types/memcached and updated ejs version (3→5) warrant testing of rendering and caching functionality.

Start review at: package.json. This file documents the primary intent—validate the version constraints align with your project's Node.js support policy and deployment targets, especially given the husky downgrade and Node.js requirement changes in several packages.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud