Update config to work with v1beta1 changes

[0sewa0]

• Updates the config files for the dynatrace-operator to match the ones on dynatrace-operator/master.
• Updates the values.yaml to match the v1beta1 CR
• Updates questions.yaml for Rancher

[chrismuellner]

I no longer have a Dynakube when upgrading from v0.2.2 with v1alpha1 to the local version with v1beta1 via the helm upgrade dynatrace-operator "helm-charts/dynatrace-operator/chart/default" -n dynatrace --reuse-values command.

It tries to apply the following manifest (not relevant sections removed):

# Source: dynatrace-operator/templates/Common/customresource-dynakube.yaml
# Copyright 2020 Dynatrace LLC
...
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
...
spec:
  apiUrl: <removed>

  tokens: dynakube

  oneAgent:
    classicFullStack:

      autoUpdate: 
  kubernetesMonitoring:
    enabled: true
    replicas: 1
  routing:
    enabled: true
    replicas: 1

This is not recognized as a valid object by Kubernetes and fails to apply, since autoUpdate does not have a value.