DG-1869 Evaluates API cache optimisation.

[hr2904]

Change description

In simple usecase of evaluates API from UI, multiple entities with same entityGuid or entityId were being fetched. for each entityGuid or entityId, we were fetching AtlasEntityHeader from DB, which was unnecessary as calls for same entityGuid or Id were redundant, thus added caching to optimise the flow.

Type of change

• Bug fix (fixes an issue)

Related issues

Fix Ticket
Testcases

Checklists

Development

• Lint rules pass locally
• Application changes have been tested thoroughly
• Automated tests covering modified code pass

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

Code review

• Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
• "Ready for review" label attached and reviewers assigned
• Changes have been reviewed by at least one other contributor
• Pull request linked to task tracker where applicable