Update auto-deploy-image to v2.14.0

What does this MR do and why?

A routine update of auto-deploy-image.

New features and fixes since v2.12.0:

Features:

• Support for service accounts in the worker deployments, see gitlab-org/cluster-integration/auto-deploy-image!210 (merged)
• Support for initContainers for all deployments, see gitlab-org/cluster-integration/auto-deploy-image!218 (merged)

Fixes:

• Add missing default value ROLLOUT_RESOURCE_TYPE=deployment gitlab-org/cluster-integration/auto-deploy-image!215 (merged)

Manual QA

--> Pipeline <--

For this .gitlab-ci.yml:

stages:
  - build
  - test
  - deploy  # dummy stage to follow the template guidelines
  - review
  - dast
  - staging
  - canary
  - production
  - incremental rollout 10%
  - incremental rollout 25%
  - incremental rollout 50%
  - incremental rollout 100%
  - performance
  - cleanup

include:
  - template: Jobs/Build.gitlab-ci.yml
  - remote: https://gitlab.com/gitlab-org/gitlab/-/raw/update-ado-image-to-2-14-0/lib/gitlab/ci/templates/Jobs/DAST-Default-Branch-Deploy.gitlab-ci.yml
  - remote: https://gitlab.com/gitlab-org/gitlab/-/raw/update-ado-image-to-2-14-0/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml
  - template: Security/DAST.gitlab-ci.yml

Note: I did not deploy an ingress, so the DAST job failed as expected.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.