Merge branch 'docs-secure-tier-add' into 'master'

Add tier badges to Secure docs

See merge request gitlab-org/gitlab!62770

doc/user/application_security/api_fuzzing/create_har_files.md

@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: howto
 ---
 
-# HTTP Archive format
+# HTTP Archive format **(ULTIMATE)**
 
 HTTP Archive (HAR) format files are an industry standard for exchanging information about HTTP
 requests and HTTP responses. A HAR file's content is JSON formatted, containing browser interactions
@@ -15,7 +15,7 @@ The HAR files can be used to perform [web API Fuzz Testing](index.md#http-archiv
 your [GitLab CI/CD](../../../ci/README.md) pipelines.
 
 WARNING:
-**DANGER** A HAR file stores information exchanged between web client and web server. It could also
+A HAR file stores information exchanged between web client and web server. It could also
 store sensitive information such as authentication tokens, API keys, and session cookies. We
 recommend that you review the HAR file contents before adding them to a repository.
 
@@ -36,7 +36,7 @@ automatically record your network activity and generate the HAR file:
 1. [Firefox web browser](#firefox-web-browser).
 
 WARNING:
-**DANGER** HAR files may contain sensitive information such as authentication tokens, API keys, and
+HAR files may contain sensitive information such as authentication tokens, API keys, and
 session cookies. We recommend that you review the HAR file contents before adding them to a
 repository.
 

doc/user/application_security/cve_id_request.md

@@ -5,7 +5,7 @@ group: Vulnerability Research
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# CVE ID Requests
+# CVE ID Requests **(ULTIMATE SAAS)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/41203) in GitLab 13.4, only for public projects on GitLab.com.
 

doc/user/application_security/offline_deployments/index.md

@@ -5,7 +5,7 @@ group: Static Analysis
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# Offline environments
+# Offline environments **(ULTIMATE SELF)**
 
 It's possible to run most of the GitLab security scanners when not connected to the internet.
 

doc/user/application_security/terminology/index.md

@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---
 
-# Secure and Protect terminology
+# Secure and Protect terminology **(FREE)**
 
 This terminology list for GitLab Secure and Protect aims to:
 

doc/user/application_security/vulnerabilities/severities.md

@@ -5,7 +5,7 @@ group: Threat Insights
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# Vulnerability severity levels
+# Vulnerability severity levels **(ULTIMATE)**
 
 GitLab vulnerability analyzers attempt to return vulnerability severity level values whenever
 possible. The following is a list of available GitLab vulnerability severity levels, ranked from