🪲 SPIKE: Investigate potential concurrency issue in environments with large number of vulnerabilities

[jmwatts]

Related user story

In the QA Wolf Premium environment, the vulnerabilities cron job is taking 2 hours to run (possibly due to how many vulnerabilities are in there). At some point while the job is running, there is a concurrency issue. Timeouts are likely being exceeded causing strange behavior. While the job is running, users observe "No vulnerabilities" when going to Software >> Vulnerabilities. This is related to #26721

Task

Determine if there is a concurrency issue or something else causing "No vulnerabilities" to show when running the vulnerabilities cron job in an environment with a large number of vulnerabilities.

Condition of satisfaction

Reproducible steps that allow us to see this behavior.

[mostlikelee]

pulling this back on the drafting board, will see if it is resolved after implementing #26404