fix: Introducing a new lock for stakeholders' cache generation

[andrea-deri]

This PR contains a new feature on cache generation that provide more stability during parallel processes. This new feature permits to define a lock on stakeholder's cache generation in order to avoid wrong concurrent cache generation that saturate memory. The lock can be applied at the level of all stakeholders or at the level of individual stakeholders, allowing for a more granular block if necessary.

List of Changes

• Defined lock strategy for stakeholder's schema cache generation
• Defined property to extend a single lock to all stakeholders
• Including more verbosity on API-level logs
• Including logs for locking and unlocking process

Motivation and Context

This change is made in order to try to mitigate a resource issue on application during parallel API calls

How Has This Been Tested?

• Tested in local environment
• Tested in DEV environment
• Tested in UAT environment

Screenshots (if appropriate):

Types of changes

• 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)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[aomegax]

🔝