Reschedule DropInvalidVulnerabilities and track jobs

What does this MR do?

After merging !60023 (merged) we found out that there were 1615 records left in the database, this could be related to recent database incident. After consulting with Database team it was suggested to reschedule the jobs with database tracking enabled

Related to #301141 (closed)

Migration details

I copied the details from the previous MR (!60023 (merged)) and updated them slightly with the new information.

Cold cache

• Select batch: 4.728s
• Drop whole batch: 44.064s
• Drop 100 records: 692.477 ms

Warm cache

• Select batch: 17.154 ms
• Drop whole batch: 1.965 ms
• Drop 100 records: 0.835 ms

Estimated execution time

Records in table: 8 079 579
Records to delete: 1615
Batch size: 10 000
Loops: 808
Delay: 120s

(4.728s + 0.693s + 120s) + 759 * (0.017s + 0.001s + 120s) ~= 96840 seconds
96840/3600 ~= 26.9 hours

Does this MR meet the acceptance criteria?

Conformity

• I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)