Nest insecure key under tls key (#3)

This fixes a key error parsing config files introduced by a breaking change in
open-telemetry/opentelemetry-collector#4063

Author: twunderlich-grapl

examples/nomad/otel-agent.nomad

@@ -91,7 +91,8 @@ receivers:
 exporters:
   otlp:
     endpoint: "{{ with service "otel-collector" }}{{ with index . 0 }}{{ .Address }}:{{ .Port }}{{ end }}{{ end }}"
-    insecure: true
+    tls:
+      insecure: true
     sending_queue:
       num_consumers: 4
       queue_size: 100

examples/nomad/otel-collector.nomad

@@ -146,7 +146,8 @@ exporters:
     endpoint: "http://somezipkin.target.com:9411/api/v2/spans" # Replace with a real endpoint.
   jaeger:
     endpoint: "somejaegergrpc.target.com:14250" # Replace with a real endpoint.
-    insecure: true
+    tls:
+      insecure: true
 service:
   extensions: [health_check, zpages]
   pipelines:

examples/nomad/otel-demo.nomad

@@ -213,7 +213,8 @@ exporters:
 
   jaeger:
     endpoint: "{{ with service "grpc.otel-demo-jaeger" }}{{ with index . 0 }}{{ .Address }}:{{ .Port }}{{ end }}{{ end }}"
-    insecure: true
+    tls:
+      insecure: true
 
 processors:
   batch:
@@ -360,7 +361,8 @@ receivers:
 exporters:
   otlp:
     endpoint: "{{ with service "otlp.otel-demo-collector" }}{{ with index . 0 }}{{ .Address }}:{{ .Port }}{{ end }}{{ end }}"
-    insecure: true
+    tls:
+      insecure: true
   logging:
     loglevel: debug