Use cache_key for invalidating LC report
What does this MR do?
To improve implementation in !18960 (merged)
Instead of going through all entities in db to create unique key for cache we use cache_key from rails. That was not possible because table didn't have created_at and updated_at before.
Related migrations
Screenshots
Does this MR meet the acceptance criteria?
When we hit end point refreshed changes to license policy reflected in Mr widget
Conformity
-
Code review guidelines -
Merge request performance guidelines -
Style guides s.html#separation-of-ee-code)