Resolve cross join in ScheduleMarkDroppedAsResolvedService

What does this MR do and why?

This MR splits the projects query in the mark dropped as resolved service so that archived projects can be excluded without a cross join between sec and main DB's.

The query performance is good as it runs on a single project id and is a highly scoped, well known query format.

MR acceptance checklist

Please 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 #481468 (closed)

Merge request reports

Loading