Database semantic convention stability implementation tracking issue

[trask]

Database semantic convention stability implementation tracking issue

• Implement some of the stable database semantic conventions #11575
• Database stable semconv tests and fixes #12601
• Use OTEL_SEMCONV_RC_OPT_IN instead of OTEL_SEMCONV_STABILITY_OPT_IN until database semconv is actually marked stable to avoid confusion(?)
• Simplify db getter and extractor hierarchy #12602
• Db network attributes #12605
• Implement the db.client.operation.duration metric #12802
• Implement the error.type and db.response.status_code attributes (see [SqlClient] Add error.type and db.response.status_code attributes opentelemetry-dotnet-contrib#2262)
• Implement the db.query.summary attribute (requires updating the jflex sql parsing)
• Implement db.operation.batch.size
• Implement span name fallbacks
• Implement Don't capture db.operation.name and db.collection.name from query formats that support multiples semantic-conventions#1566
• Implement Add section on span status for databases semantic-conventions#1560
• Implement Remove redis database index from redis span name semantic-conventions#1565
• Implement Introduce generic operation.name attribute to represent span name semantic-conventions#1567
• Implement [database] reporting stored procedures/prepared statements semantic-conventions#1491
• Upstream experimental db.namespace definitions to semconv repo for all of the supported instrumentations

[zeitlinger]

@trask @laurit which of these items are ready to be implemented?

[trask]

I think most of them, would love your help, pick any and DM me or post on #otel-semconv-db-client-stability with any questions!

[zeitlinger]

OK, I'll try #12802