Caching layer for participant context config #5311
Description
Feature Request
We should implement a caching layer for the ParticipantContextConfig to avoid hitting the database too much when resolving config keys at runtime
Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
If possible, provide a (brief!) solution proposal.