doc: link to GitLab JUnit integration changed

* a **build** job (mandatory) mapped on the `build` stage that builds the code (if applicable for the language) and runs the unit tests.<br/>

  Unit Tests should support the following GitLab CI features:

    * unit tests report integration using [JUnit test report](https://docs.gitlab.com/ee/ci/junit_test_reports.html)

    * unit tests report integration using [JUnit test report](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportsjunit)

    * code coverage computing and [integration](https://docs.gitlab.com/ee/ci/yaml/#coverage)

* any number of **code analysis** jobs (optional) mapped on the `test` stage that allow triggering language specific code analysis tools

  ([SAST](https://en.wikipedia.org/wiki/Static_program_analysis), dependency check, ...)

Those jobs should implement the following features:

* tests report integration using [JUnit test report](https://docs.gitlab.com/ee/ci/junit_test_reports.html)

* tests report integration using [JUnit test report](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportsjunit)

* auto-evaluating the environment url to test based on the presence of `$environment_url` (possibly propagated by an upstream deployment template

using [dotenv artifacts](https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#artifactsreportsdotenv)) or a `environment_url.txt` file.

| [artifacts](https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html) | Every template implements optimized artifacts policy to keep only the bare necessities. |

| [interruptible](https://docs.gitlab.com/ee/ci/yaml/#interruptible) | Every interruptible job implements the `interruptible` feature to allow cancelling the pipeline as soon as a newer one is triggered. |

| [code coverage](https://docs.gitlab.com/ee/ci/yaml/#coverage) | Every build&test job enforces code coverage computing (using the required build tools and options), and integration to GitLab (visible in merge requests and as a [badge](https://docs.gitlab.com/ee/ci/pipelines/settings.html#test-coverage-report-badge)). |

| [JUnit test reports](https://docs.gitlab.com/ee/ci/junit_test_reports.html) | Every test job produces - whenever possible - a JUnit report, so that your test reports are automatically integrated to your pipelines and merge requests. |

| [JUnit test reports](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportsjunit) | Every test job produces - whenever possible - a JUnit report, so that your test reports are automatically integrated to your pipelines and merge requests. |

| [code quality](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html) | Every code quality job produces - whenever possible - a Code Climate report, so that your code quality reports are automatically integrated to your pipelines and merge requests. |

| [environments](https://docs.gitlab.com/ee/ci/environments/) | Every deployment job declares the deployed environment to GitLab. They also implement a cleanup job for ephemeral environments, that can be triggered manually and also automatically on branch deletion. |

| [resource_group](https://docs.gitlab.com/ee/ci/yaml/#resource_group) | Every deployment job implements the `resource_group` feature to prevent concurrent jobs deploying at the same time on the same environment. |