Deprecate and eventually delete the Tanzu Observability Exporter

[atoulme]

          Hi @atoulme, our nearish-term plan is to deprecate and eventually delete the Tanzu Observerability Exporter. We have better ways to ingest native OTLP protobufs now, so OTel Collector users can just switch to the OTLP Exporter if needed. I believe @keep94 is the one who will be doing the deprecation PR, followed by the eventual deletion PR.

Originally posted by @oppegard in #23395 (comment)

• Open a PR to mark the component as deprecated
• Open a PR to delete the component after deprecation period.

[github-actions]

Pinging code owners for exporter/tanzuobservability: @oppegard @thepeterstone @keep94. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[atoulme]

@keep94 would you please signal if you're looking to work on this?

[keep94]

@atoulme No, I don't plan to work on this during this quarter.

[atoulme]

@keep94 next quarter maybe then? Please let us know, see #23395 for context. We will need to assess by January 2024 what to do with the component.

[atoulme]

@oppegard ok to open a PR to delete the exporter?

[oppegard]

@atoulme the deprecation warning in the exporter's readme states that it will be unavailable after 2023. I'd prefer to wait until the beginning of next year for deleting.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[atoulme]

This has been completed. Closing.