Add logging for running policy violations after merge
What does this MR do and why?
Add logging for running policy violations after merge.
In order to detect edge cases which leave scan_result_policy_violations stuck in the running state, this change adds logging in case we detect any running violations after a merge request gets merged.
It is important to know about these cases and address them to prevent stuck merge requests with policy_mergability_check feature flag enabled.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
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 #504700 (closed)