Update configs+readmes to reflect de-squash of tls

[justaverylee]

Changed some example/test configs which did not compile since the tls struct (under grpc config) was changed from squashed to not squashed in the main parent repo (not -contrib). All changes are indenting insecure or other tls properties under the tls label.

Link to tracking Issue:
In parent repo the issue causing these errors are discussed in this issue: open-telemetry/opentelemetry-collector#4028
And specifically this merge: open-telemetry/opentelemetry-collector#4063

There is an issue in this (-contrib) repo discussing this: #5385

Testing:
No changes. Some example configs and readme demo configs now pass the config validation at startup.

Documentation:
Updated appropriate readmes to match change described above. Let me know if I missed some!

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Avery Gottesman (d073e11)

[hyunuk]

Thanks for the PR! I was looking for the similar issue and I found these files also needs to be updated.

exporter/datadogexporter/example/example_k8s_manifest.yaml
exporter/elasticsearchexporter/README.md
exporter/prometheusremotewriteexporter/README.md
extension/awsxrayproxy/README.md
extension/awsxrayproxy/testdata/config.yaml
extension/oauth2clientauthextension/README.md
receiver/awsxrayreceiver/README.md
receiver/awsxrayreceiver/testdata/config.yaml

Just wanted to let you know that I'm currently working on this issue since some of config.go files in each components haven't been applied this changes you mentioned, extension/awsxrayproxy and receiver/awsxrayreceiver will fail on tests if you make change in these files above.