Fix reverted cache scheme changes
We made a change to modify the cache to use immutable keys which was merged with the related MR.
During rollout, we found that there was an inconsistency between canary and production. We found that the problem was due to canary using a different cache scheme from Sidekiq. To roll this out we might need a transition period where Sidekiq invalidates the cache on both schemes, unless there is another alternative.
This issue is to replace the reverted code and detail how to roll out the changes.