Open Telemetry: Steps to GA a feature

[sourabh1007]

Traces

• Update isStable flag here
• Make sure, by default, open telemetry attributes are getting emitted are same as mentioned in open telemetry docs https://opentelemetry.io/docs/specs/semconv/database/cosmosdb/
• Make sure backward compatibility is there, there should be a way to get back appinsights supported attributes. Preferably, as mentioned in this PR.
• Review observability documentation https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/docs/observability.md#net-sdk-observability-feature-design and https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/sdk-observability and make sure it talks about:
  a) Versioning
  b) Event Source and Activity Source Name
• Make sure Samples are available in this repo.

Metrics

• Make sure, by default, open telemetry metrics are getting emitted are same as mentioned in open telemetry docs https://opentelemetry.io/docs/specs/semconv/attributes-registry/db/
• Review observability documentation https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/docs/observability.md#net-sdk-observability-feature-design and remove client telemetry feature, related information.
• Make sure Samples are available in this repo.

[jcocchi]

This list looks good to me! You have versioning partially covered with the backwards compatibility item, but it might be good to call out versioning story explicitly as a work item as well.

Not a GA blocker, but we should also double check that the Azure Montior UI still works well with the new OTel traces and attributes. They had some special mapping of our database/ collection for example, and the OTel attribute names have changed.