Improve lookup for component usages
What does this MR do and why?
This change optimizes how the system tracks when components are last used by projects. Instead of looking up related records (like catalog_resource and component_project) during the database search, it now searches using only the essential IDs and then fills in the additional information afterward. This approach is more efficient because it reduces the complexity of the database query while still ensuring all the necessary data relationships are properly maintained.
References
Screenshots or screen recordings
NA
How to set up and validate locally
- Functionally, it is the same as before. Tests should pass and pipeline should be
🍏
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #561462