Update the `strapi-plugin-rest-cache` devDependency in package.json

[geeky-biz]

The older strapi-plugin-rest-cache has a peerDependency of Strapi v4 (specifically "^4.0.5") but the latest version of strapi-plugin-navigation has a Strapi devDependency of "^5.14.0". This results in dependency conflict when trying npm install as below:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: strapi-plugin-navigation@3.2.4
npm error Found: @strapi/strapi@5.26.0
npm error node_modules/@strapi/strapi
npm error   dev @strapi/strapi@"^5.14.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @strapi/strapi@"^4.0.5" from strapi-plugin-rest-cache@4.2.9
npm error node_modules/strapi-plugin-rest-cache
npm error   dev strapi-plugin-rest-cache@"^4.2.9" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error

With the new @strapi-community/plugin-rest-cache now available for Strapi v5, updating this dependency shall address the dependency conflict issue.

[cyp3rius]

@mateusz-kleszcz would you update that and release a minor version, please?

[mateusz-kleszcz]

@geeky-biz I’ve created a PR with this fix — could you please check if it works for you?

[geeky-biz]

@mateusz-kleszcz Your change addressed the error I encountered on npm install

But I could not test if caching works with the new v5 plugin like it did earlier. I wanted to check if specifically the code in server/src/cache/index.ts works as-is. But, unfortunately I could not get the new caching plugin to work with my local Strapi (the new plugin appears not very stable, it throws errors when enabled even with new a Strapi setup). If you could get the new plugin to work with your Strapi, perhaps you can verify if the caching works as expected.