Add deprecation notice for Secure template overrides

Adds notice that only/except will no longer be supported
when overriding secure templates, starting in 13.0

Relates to https://gitlab.com/groups/gitlab-org/-/epics/2300

doc/user/application_security/container_scanning/index.md

@@ -187,6 +187,10 @@ using environment variables.
 
 ### Overriding the Container Scanning template
 
+CAUTION: **Deprecation:**
+Beginning in GitLab 13.0, the use of [`only` and `except`](../../../ci/yaml/README.md#onlyexcept-basic)
+is no longer supported. When overriding the template, you must use [`rules`](../../../ci/yaml/README.md#rules) instead.
+
 If you want to override the job definition (for example, change properties like
 `variables`), you need to declare a `container_scanning` job after the
 template inclusion and specify any additional keys under it. For example:

doc/user/application_security/dast/index.md

@@ -376,6 +376,10 @@ configuration, the last mention of the variable will take precedence.
 
 ### Overriding the DAST template
 
+CAUTION: **Deprecation:**
+Beginning in GitLab 13.0, the use of [`only` and `except`](../../../ci/yaml/README.md#onlyexcept-basic)
+is no longer supported. When overriding the template, you must use [`rules`](../../../ci/yaml/README.md#rules) instead.
+
 If you want to override the job definition (for example, change properties like
 `variables` or `dependencies`), you need to declare a `dast` job after the
 template inclusion and specify any additional keys under it. For example:

doc/user/application_security/dependency_scanning/index.md

@@ -115,6 +115,10 @@ configuration, the last mention of the variable will take precedence.
 
 ### Overriding the Dependency Scanning template
 
+CAUTION: **Deprecation:**
+Beginning in GitLab 13.0, the use of [`only` and `except`](../../../ci/yaml/README.md#onlyexcept-basic)
+is no longer supported. When overriding the template, you must use [`rules`](../../../ci/yaml/README.md#rules) instead.
+
 If you want to override the job definition (for example, change properties like
 `variables` or `dependencies`), you need to declare a `dependency_scanning` job
 after the template inclusion and specify any additional keys under it. For example:

doc/user/application_security/sast/index.md

@@ -143,6 +143,10 @@ the pipeline configuration, the last mention of the variable will take precedenc
 
 ### Overriding the SAST template
 
+CAUTION: **Deprecation:**
+Beginning in GitLab 13.0, the use of [`only` and `except`](../../../ci/yaml/README.md#onlyexcept-basic)
+is no longer supported. When overriding the template, you must use [`rules`](../../../ci/yaml/README.md#rules) instead.
+
 If you want to override the job definition (for example, change properties like
 `variables` or `dependencies`), you need to declare a `sast` job after the
 template inclusion and specify any additional keys under it. For example:

doc/user/compliance/license_compliance/index.md

@@ -154,6 +154,10 @@ directory of your project.
 
 ### Overriding the template
 
+CAUTION: **Deprecation:**
+Beginning in GitLab 13.0, the use of [`only` and `except`](../../../ci/yaml/README.md#onlyexcept-basic)
+is no longer supported. When overriding the template, you must use [`rules`](../../../ci/yaml/README.md#rules) instead.
+
 If you want to override the job definition (for example, change properties like
 `variables` or `dependencies`), you need to declare a `license_scanning` job
 after the template inclusion and specify any additional keys under it. For example: