add forgotten helmfile config, add `--validate=false` to kubernetes manifests (https://github.com/jetstack/cert-manager/issues/2208)

Resolve "Use prometheus' default securityContext"

Closes #305

See merge request openappstack/openappstack!117

Resolve "Revert changes from !100"

Closes #339 and #355

See merge request openappstack/openappstack!115

Increase nextcloud install timeout to 15m

Closes #354

See merge request openappstack/openappstack!121

Closes: #305

Now that helm is working again for our usecase (see details in
https://open.greenhost.net/openappstack/openappstack/issues/339)
we can install helm as snap again.

Closes: #339

This reverts commit 52910021.

Resolve "Prometheus installation can not be repeated"

Closes #351

See merge request openappstack/openappstack!112

Resolve "Use gitlab issue instead of limesurvey for user feedback"

Closes #326

See merge request openappstack/openappstack!109

Resolve "improve test instructions"

Closes #349

See merge request openappstack/openappstack!110

Resolve "Create MR release template"

Closes #345

See merge request openappstack/openappstack!105

Resolve "Increase Nextcloud livenessProbe's leniency"

Closes #350

See merge request openappstack/openappstack!111

make separate commands for each helmfile to apply, so we can make sure local storage and nginx exists before monitoring, but nextcloud is made after monitoring

Resolve "Creating cluster fails if the hostname is `oas-dev`"

Closes #346

See merge request openappstack/openappstack!106

Resolve "kube_config_cluster.yml should be copied to local machine earlier"

Closes #319

See merge request openappstack/openappstack!104

update prometheus and helm apply it with force as per the upgrading instructions from version 5 to 6

Resolve "Tag 0.2.0"

Closes #342

See merge request openappstack/openappstack!103