Rename feature: Pre-receive Secret Detection to Secret Push Protection

What change is being made?

This MR renames the "Pre-receive Secret Detection" feature to "Secret Push Protection."

A broad range of opinions were carefully considered in Secret Detection Feature Naming (gitlab-org/gitlab#454395).

Why is this change being made?

"Pre-receive Secret Detection" (available today as an experimental feature for Dedicated customers), is a technically accurate name, but customers can not intuitively discern what the feature does from it's name. While discussing the feature with customers, we've realized that developers who know Git well may understand what "pre-receive" means, but GitLab buyers and security personas do not and are confused by the name. We would like to rename the feature in 17.1 before the beta launch, in order to improve feature adoption.

By renaming to "Secret Push Protection" we will better conform to GitLab's feature naming guidelines in the following ways:

• Having as few words as possible
• Clearly expressing what the feature is
• Be common in the industry
  • GitHub has named the feature "Push Protection," and the feature has been widely written about across the industry.
  • NIST's cybersecurity framework defines "protect" as a distinct capability in contrast to "detect."

Process

Process for Renaming Features (handbook)

Approvals

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

• Chief Product Officer @david (post MR link in chief-product-officer once all others have approved)
• PLT Leader relevant to the affected Section(s) @hbenson
• The Product Director relevant to the affected Section(s) @sarahwaldner
• The Engineering Manager relevant to the affected Section(s) @amarpatel
• The Group Engineering Manager relevant to the affected Section(s) @twoodham
• Director of Product Design @vkarnes

**Note:**_ Chief Product Officer approval should be requested once all other approvals have been completed. To request approval, post the MR link in the #chief-product-officer channel tagging @david and cc'ing @Gena Schwam._

The following people need to be on the merge request so they stay informed:

• Chief Technology Officer @sabrinafarmer
• Development Leader relevant to the affected Section(s) @bmarnane
• VP of Infrastructure & Quality Engineering @meks
• VP of UX @ampesta
• Director of Technical Writing @susantacker
• Engineering Productivity @gl-quality/eng-prod
• The Product Marketing Manager relevant to the stage group(s) @dsteer

After Approvals and Merge

• Create an issue in the gitlab-org/quality/triage-ops project to update GitLab Bot automation:
  • for Category change
  • for Stage or Group change
  • If label migration is required, please follow the self-serve instructions to get started on a one-off label migration MR
• Open an MR in the gitlab-org/gitlab project to update any reference of the previous group label to the new one
• Mention the product group Technical Writer to update the documentation metadata
• Share MR in #product, #development, and relevant #s_, #g_, and #f_ Slack channels