Docs: Add Advanced SAST to feature list, edit feature names

What does this MR do?

• Add Advanced SAST to the features-by-tier table for SAST.
• Change the features from <Verb> ... to noun forms. This is because I didn't have a great way to list "cross-file, cross-function scanning" in a verb-centered format, but also didn't want to have a table full of verbs with a single noun-based feature name.
• Condense a few of the feature items.
• Add links to related sections for MR widget and MR changes view.

Related issues

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

added devopssecure docs-only docsimprovement documentation groupstatic analysis maintenancerefactor sectionsec typemaintenance labels

assigned to @connorgilbert

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/user/application_security/sast/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

changed milestone to %17.5

added Category:SAST label

@rdickenson – would love your thoughts on this one. I debated a bit on the phrasing of the table entries, as mentioned in the description of the MR.

requested review from @rdickenson

resolved all threads

approved this merge request

started a merge train

Hi @rdickenson ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. You're welcome to improve it.

added Technical Writing label

merged

mentioned in commit fe359a99

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label

mentioned in epic gitlab-org#15401

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label