"Bring your own Jaeger" page uses incorrect OT collector schema

The ["Bring your own Jaeger" section](https://linkerd.io/2.11/tasks/distributed-tracing/#bring-your-own-jaeger) suggests the following config:
```
jaeger:
enabled: false

collector:
config: |
receivers:
otlp:
protocols:
grpc:
http:
opencensus:
zipkin:
jaeger:
protocols:
grpc:
thrift_http:
thrift_compact:
thrift_binary:
processors:
batch:
extensions:
health_check:
exporters:
jaeger:
endpoint: my-jaeger-collector.my-jaeger-ns:14250
insecure: true
service:
extensions: [health_check]
pipelines:
traces:
receivers: [otlp,opencensus,zipkin,jaeger]
processors: [batch]
exporters: [jaeger]
```
However, the proper schema for the "insecure" field in the jaeger exporter is:
```
jaeger:
tls:
insecure: true
```

Open the linked “Bring your own Jaeger” section in the distributed-tracing documentation and review the embedded collector YAML. Update the Jaeger exporter’s insecure setting to the documented nested tls schema, then verify that the rendered example matches the intended collector configuration.

Written by the indexing model from the issue text.