Rename the "security dashboard" to "vulnerability list"

Summary

This may be a controversial statement, but here goes. Our security dashboard isn't a security dashboard, it's a list of vulnerabilities.

When we planned to create the security dashboard, there were charts and stats and all sorts that made it an actual dashboard. But the boring solution meant that (for now) the dashboard was just a list of vulnerabilities.

Calling this list the security dashboard is largely fine, but here's a few issues I have with it.

  1. It's inconsistent with our dependency list and licence list features.
  2. With the addition of standalone vulnerabilities the URLs are a bit weird. e.g. https://gitlab.com/gitlab-org/gitlab/security/dashboard/123 would link to a vulnerability.
  3. There's a lot more to security than vulnerabilities now, calling this the security dashboard makes it sound like it does more than it actually does. There's no dependency, licence, or threat monitoring information in here

My proposal is to rename "security dashboard" to "vulnerability list" and update the urls accordingly. e.g https://gitlab.com/gitlab-org/gitlab/security/dashboard/123 becomes https://gitlab.com/gitlab-org/gitlab/vulnerabilities/123 We should also put in redirects for anyone that's bookmarked the old routes.

Improvements

Making the suggested change would do a few things for us:

  1. It would fix the issues I listed above.
  2. It leaves space for us to create a true security dashboard, like the original designs intended.

Risks

  1. Existing URLs would be different. Though we can circumvent that with redirects.
  2. There would be a lot of name changes in the code to reflect the new naming scheme. We'd need to make sure our tests are solid and QA is aware of the impending changes.
  3. Customers may be initially confused by the change.

Involved components

TBC, there's a few though.

Edited by Sam Beckham