Update cache dependency paths in CI workflow

[mubking]

Description

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Refactoring (no functional changes)
• ⚡ Performance improvement
• 🧪 Test addition or update

Related Issues

Closes #

Changes Made

Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Test Steps

Breaking Changes

Breaking Changes:

Migration Guide:

Screenshots/Demo

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published
• I have checked for breaking changes and documented them if applicable

Additional Notes

[ogazboiz]

hey @mubking, this is a duplicate of #212 — same change, same issue.

the cache-dependency-path should point to the lock file (package-lock.json), not package.json. changing it to package.json is the wrong fix.

the correct approach:

1. make sure frontend/package-lock.json and backend/package-lock.json exist (run npm install in each directory)
2. commit those lock files
3. revert cache-dependency-path back to pointing at the lock files

please close this PR and the other duplicates (#212, #214) and open one clean PR with the right fix. happy to review it quickly!

also come chat with us on Telegram: https://t.me/+DOylgFv1jyJlNzM0