Use GKE 1.22 environment for production (revised)

What does this MR do?

Run chart tests in GKE 1.22 environments for master branch along with GKE 1.20. Second attempt. Note, the first attempt at this MR failed https://gitlab.com/gitlab-org/charts/gitlab/-/pipelines/755392611 and was reverted. This version remove the check for an existing DNS entry for the cluster as the code will create the entry if it does not already exist. We also add in the manual full QA test triggers from !2926 (merged).

Related issues

• Closes #3690 (closed)
• Related !2910 (merged)
• Related !2936 (merged)
• Related !2926 (merged)

Test plan

• Green pipeline on gitlab.com (including triggering full qa test suites).
• Run stable_gke122 without existing DNS entries (requires .gitlab-ci.yaml hack)
• Run stable_gke122 with existing DNS entries (requires .gitlab-ci.yaml hack).

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• Merge Request Title and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added
• Integration tests added to GitLab QA
• Equivalent MR/issue for omnibus-gitlab opened
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.