Deprecate the opentelemetry-collector chart

[TylerHelmuth]

The Honeycomb opentelemetry-collector chart was created before a community opentelemetry-collector chart existed and filled the important need to easily deploy a collector that could export data to Honeycomb.

Today there is an OpenTelemetry Community Collector helm chart that is actively maintained and supports more features than our chart. In addition, exporting data to Honeycomb via the OpenTelemetry Collector has been simplified to the OTLP exporter with a small amount of configuration. At this time the only "advantage" our chart has is the ability to configure the OTLP exporter based on the user-supplied API key and dataset name. But the advantage comes at the cost of lack of useful k8s features, automatic complex component support (see the community chart's preset concept for more details`), and regular updates.

I propose we deprecate our opentelemetry-collector chart in favor of the community opentelemetry-collector chart, supplementing the Honeycomb-specific configuration that our chart provided with Honeycomb documentation. Instead of investing our time in our own chart, we invest our time helping maintain the OpenTelemetry community chart.