[autoinstrumentation, collector] Improve Auto Instrumentation interaction with Collector Daemonset

[TylerHelmuth]

While doing some investigations with Auto Instrumentation injection and the OpenTelemetryCollector as a daemonset I found some improvements I think we should make to improve the experience.

• Allow the daemonset Collector to use hostPort so that hostNetwork is not required. This slightly reduces the security impact, reduces required configuration for the user who wants to connect using NODE IP, and aligns with the helm chart's default daemonset instance.
• Create some documentation about how Auto Instrumentaiton instances should connect to different deployment patterns. I think this should be on the docs site and linked to from our README.
• Add node_ip via the downward API automatically to the auto instrumentation injected env vars. We already inject Node name so including node IP shouldn't be an issue. Doing this automatically allows users to reference the value without having to define it themselves.
• Assist with connecting to a collector. Instead of requiring the user to specify the endpoint, provide some more user-friendly options that leverage the Operator to do some setup. Some ideas:
  • Allow the user to specify the name of a collector to export to. The Operator will validate that it exists and then setup the endpoint (idea from @jaronoff97)
  • Allow the user to specify they want to connect to a daemonset instance of the collector. The Operator will validate that it exists and setup the endpoint.

[jaronoff97]

As part of this, we should also enable setting the internalTrafficPolicy which i believe would be the cleanest implementation as well