EE Port: Docs: Fix link references for artifacts

doc/ci/examples/browser_performance.md

@@ -41,7 +41,7 @@ The above example will create a `performance` job in your CI/CD pipeline and wil
 Sitespeed.io against the webpage you defined in `URL` to gather key metrics.
 The [GitLab plugin](https://gitlab.com/gitlab-org/gl-performance) for
 Sitespeed.io is downloaded in order to save the report as a
-[Performance report artifact](../../ci/yaml/README.md#artifactsreportsperformance)
+[Performance report artifact](../yaml/README.md#artifactsreportsperformance-premium)
 that you can later download and analyze.
 Due to implementation limitations we always take the latest Performance artifact available.
 

doc/ci/examples/code_quality.md

@@ -36,7 +36,7 @@ code_quality:
 
 The above example will create a `code_quality` job in your CI/CD pipeline which
 will scan your source code for code quality issues. The report will be saved as a
-[Code Quality report artifact](../../ci/yaml/README.md#artifactsreportscodequality)
+[Code Quality report artifact](../yaml/README.md#artifactsreportscodequality-starter)
 that you can later download and analyze.
 Due to implementation limitations we always take the latest Code Quality artifact available.
 

doc/ci/examples/container_scanning.md

@@ -51,7 +51,7 @@ The above example will create a `container_scanning` job in your CI/CD pipeline,
 the image from the [Container Registry](../../user/project/container_registry.md)
 (whose name is defined from the two `CI_APPLICATION_` variables) and scan it
 for possible vulnerabilities. The report will be saved as a
-[Container Scanning report artifact](../../ci/yaml/README.md#artifactsreportscontainer_scanning)
+[Container Scanning report artifact](../yaml/README.md#artifactsreportscontainer_scanning-ultimate)
 that you can later download and analyze.
 Due to implementation limitations we always take the latest Container Scanning artifact available.
 

doc/ci/examples/dast.md

@@ -40,7 +40,7 @@ dast:
 The above example will create a `dast` job in your CI/CD pipeline which will run
 the tests on the URL defined in the `website` variable (change it to use your
 own) and scan it for possible vulnerabilities. The report will be saved as a
-[DAST report artifact](../../ci/yaml/README.md#artifactsreportsdast)
+[DAST report artifact](../yaml/README.md#artifactsreportsdast-ultimate)
 that you can later download and analyze.
 Due to implementation limitations we always take the latest DAST artifact available.