Count mismatch between current day and other days on Security Dashboard

Summary

The count of vulnerabilities presented on a chart on Security Dashboard has a mismatch between current day and all the other days - there appears to be no continuity between these data points and the data seems wrong/sourced differently.

Example:

Steps to reproduce

1. Visit "Security Dashboard" on any project having some detected vulnerabilities - with high enough count there should be a visible discrepancy between counts on present day and all the remaining days.

What is the current bug behavior?

Incorrect counts on the current day (no data point continuity).

What is the expected correct behavior?

The counts have continuity and data points are sourced using the same filtering conditions.

Relevant logs and/or screenshots

There is an investigation thread on Slack with findings summarised below:

1. Current day (D) uses different GraphQL endpoint than the data fetched for (D-1..D-30)
2. This could be due to ongoing incident and fix once the data is recalculated via cronjob (as of now this turned to be incorrect assumption)
3. Most likely introduced after merging of this MR which most likely went unnoticed due to lower discrepancies between counts for test project vs Gitlab (where this difference is huge).
4. The root cause is not having proper filter for state in vulnerabilitySeveritiesCount GraphQL query, which pulls all vulnerabilities (even RESOLVED) instead of only DETECTED and CONFIRMED.