Update auto-deploy-image to v2.17.0

What does this MR do and why?

This is a routine update of the upstream project. See gitlab-org/cluster-integration/auto-deploy-image@v2.14.0...v2.17.0

Highlights:

• Helm has been updated to 3.7 and kubectl to 1.20
• Allow selecting the context using a KUBE_CONTEXT variable. This enables YAML-less Auto DevOps to select the agent to use with GitLab's new CI/CD tunnel.
• Set a default value for KUBE_NAMESPACE when none is provided. With the CI/CD tunnel, this value is not provided by GitLab.
• Support for autoscaling/v2beta2 metrics for HPA

Manual QA

--> Pipeline <--

For this .gitlab-ci.yml:

stages:
  - build
  - test
  - deploy
  - 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-17-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-17-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.