Instead of maintaining two templates, there should be a
single source of truth.

Container Scanning, Dependency Scanning, License Management
and SAST parts of Auto DevOps now use the preexisting templates.

Auto DevOps and the DAST job template will now use a
shared job template instead of maintaining two copies
of the job. This also allows Auto DevOps to use custom
authentication with DAST.

This allows these templates to be used outside of Auto DevOps,
or easily excluded from Auto DevOps.

The security jobs in Auto DevOps differ slightly from the ones
that are already available as templates, they will be moved
next.

closes https://gitlab.com/gitlab-org/gitlab-ee/issues/6636
closes https://gitlab.com/gitlab-org/gitlab-ee/issues/5763

For some reason this value can be an empty string and we want to ensure
that we correctly fail the job before a deploy. This is particularly
problematic at the moment when coupled with
https://gitlab.com/gitlab-org/gitlab-ce/issues/54760 as the user has no
easy way to recover without destroying the cluster and starting over.

Deploy boards now will check for app.gitlab.com/env and
app.gitlab.com/app

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

We set the default value to 9.6.2 since this was the previous default
being used by `stable/postgresql --version=0.7.1` which is used in
auto-deploy-app.

Bump kubectl in Auto DevOps to 1.11.7. Minor patch upgrade from 1.11.6.

Minor bugfix release:
https://github.com/helm/helm/releases/tag/v2.12.3

- Fixes multiple typos on AutoDevops script
- Add an alias to Clusters::Cluster#domain as base_domain, so it's more
descriptive
- Removes unnecessary memoization on qa specs
- Changes migration to a post migration to deal better with traffic on
big instances (like gitlab.com)

Ensure KUBE_INGRESS_BASE_DOMAIN existence by setting his value to
AUTO_DEVOPS_DOMAIN if the first one doesnt exists. Also made
corresponding changes throughout the whole script

Related to https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24580

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Use the latest major version that will support the current clusters on
GKE which is v1.10

- DRY up setting deploy name

- DRY up application_secret_name

Use --from-env-file with bash process substitution

We still need bash as process substition (`<()`) is not available in sh

ie. fix below quoting issue:

```
kubectl create secret -n project-with-autodevops-900057eb1ce34399-77 \
  generic production-secret \
  '--from-literal=OPTIONAL_MESSAGE=You' can see this secret \
  -o yaml --dry-run
```

With fix, it should be generating:

```
kubectl create secret -n project-with-autodevops-900057eb1ce34399-77 \
  generic production-secret \
  --from-literal 'OPTIONAL_MESSAGE=You can see this secret' \
  -o yaml --dry-run
```

Call via bash -c, instead of assuming bash

The shell is /bin/sh, so we cannot asssume bash. Hence we use `bash -c`

bash is installed for deploy jobs in a prior step

Find any CI variables from `env` which has a prefix. If there are any
such CI variables, strip prefix from variable name then create a generic
Kubernetes secret containing all these CI variables as key-value pairs.

Also, Pass in secretname to application container

The secretname may be present, if nil, the chart does nothing. If
present, the chart will load the key-value pairs from the secret into
the application container. See
https://gitlab.com/charts/auto-deploy-app/blob/master/README.md#configuration

This reverts merge request
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22929

This reverts merge request !23165

This should help debug issues like
https://gitlab.com/gitlab-org/gitlab-ce/issues/54760