Use "Advanced SAST" name for SAST_ADVANCED report

What does this MR do and why?

Use "Advanced SAST" name for SAST_ADVANCED report

Changelog: changed
EE: true

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

• issue: Advanced SAST always shows as not enabled in th... (#500320 - closed) • rossfuhrman, Miranda Fluharty • 17.7 • On track
• feature documentation: https://docs.gitlab.com/ee/user/application_security/sast/gitlab_advanced_sast.html

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

1. have a GitLab Ultimate licence
2. navigate to a project that does not have Advanced SAST scanning set up
3. in the sidebar, choose Secure => Vulnerability report
4. at the top of the page, an alert should appear to list any scanners that aren't enabled for the project