Current status doc discussion

[chetanmehta94]

The current state of the doc states that the flavor of otelcollector is production tested and breaking changes to the core configuration experience for metrics and traces collection aren't expected.
https://github.com/signalfx/splunk-otel-collector/tree/main#current-status

However, it seems any deprecations or breaking changes are propagated as-is from otelcollector to splunk distribution.
For e.g.

1. (Contrib) sapmreceiver: Deprecate SAPM receiver ([receiver/sapm] Consider deprecating sapmreceiver open-telemetry/opentelemetry-collector-contrib#32125)
2. (Contrib) sqlqueryreceiver: Fail if value for log column in result set is missing, collect errors ([receiver/sqlquery] Improve error handling for missing columns in result set open-telemetry/opentelemetry-collector-contrib#35068)

Can you please clarify the stating in the doc ?

I am using splunk-otel-collector instead of otel-collector-contrib as it is production tested. Specifically using: k8sclustereceiver, kubeletstatsreceiver, otlphttpexporter. Wanted to be sure that these components are fit for production ready usage, and not expected to go into deprecated or obsolete case