Rename first_class_init to vulnerability_report_init
What does this MR do?
This MR simply renames first_class_init to vulnerability_report_init.
Why are we doing this change?
When we first rolled out the refactored security dashboards we named the vulnerabilities as first_class_vulnerabilities. This is no longer the case. As part of #321775 (closed), I thought that now it makes sense to rename these files to vulnerability_report which reflects the real page name.
Screenshots (strongly suggested)
Nothing should change visually, but here's a screenshot for all three dashboards which shows that they're still working:
| dashboard | screenshot |
|---|---|
| group |  |
| project |  |
| instance |  |
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #321775 (closed)