Maps EEC/StatsD-related annotations to the EEC and data sources runtime properties

[toszr]

Extension Controller and data sources (like StatsD) can be configured in OneAgent/ActiveGate bare metal deployments using runtime properties (a.k.a. debug flags). In a bare metal AG setup, the interface is a json file stored at /var/lib/dynatrace/remotepluginmodule/agent/conf/runtime/runtimeConfiguration.

This changeset converts EEC/StatsD debug flags defined as DynaKube annotations with prefix alpha.operator.dynatrace.com/extensions. into valid runtime properties mounted into EEC container via a config map.

Example:

    "alpha.operator.dynatrace.com/extensions.debugExtensionDSstatsdlogoutboundminttraffic": "true"

is turned into:

apiVersion: v1
kind: ConfigMap
metadata:
  name: eec-config
  namespace: dynatrace
data:
  runtimeConfiguration: |
    {
      "revision": 1,
      "booleanMap": {
        "debugExtensionDSstatsdlogoutboundminttraffic": true
      },
      "stringMap": {},
      "longMap": {}
    }

[chrismuellner]

Annotations starting with internal.operator... should be managed by the operator.
If these annotations are defined by the user, we need to find a different name.

[toszr]

OK, changed the prefix to alpha.operator.dynatrace.com/extensions..

Implemented changes from review