feat(cache): add a mutex utility and prevent parallel processing with the same cache key

[secustor]

Changes

• Adds a mutex implementation based on our cache key system.
• This PR also adds the lock usage to the cache decorator

Context

This prevents race conditions where we have cache miss and then multiple stacks are getting the same packages.
Where this can have a big impact are where we are limited on API calls or lookups are expensive until cached.
e.g. Terraform artifact updates, lookups for the deb datasource.

It could be interesting for the bigger installations to extend this to Redis later on so this is also the case if multiple instances share the same cache.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[viceice]

otherwise LGTM

[renovate-release]

🎉 This issue has been resolved in version 38.39.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 38.39.0

Your semantic-release bot 📦🚀