DB: fix how operation and collection names are recorded for complex queries (opt-in db.query.text on metrics, new db.query.summary recommended attribute)

[lmolkova]

Fixes #1159, #805

Related: #521

Based on the discussion on slack https://cloud-native.slack.com/archives/C06HH05KNMC/p1728891505239829 and spec discussion on 10/25/24:

• having a single operation/collection name on metrics is not enough
• it provides a baseline that works for nosql and sql with simple queries
• it can work better if/once we provide a way for users to supply their own operation alias/other context
• it's misleading to record one operation/collection when in fact there are multiple

We can however:

• allow users to enable capturing sanitized value of a db.query.text as opt-in to mitigate shortcomings of single operation/collection name.
• create a synthetic query text from a combination of operations and collections (like SELECT foo, UPDATE bar, DELETE bar - it'd have low-ish cardinality, would be shorter than a query, won't have any sensitive information that needs sanitization and would be readable enough. This allows to make it recommended on metrics.

This PR implements both options as discussed in #805 (comment)

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[trask]

some possibilities for naming:

• db.query.synthetic
• db.query.short
• db.query.summary
• db.query.description

[lmolkova]

I really like the db.query.summary - it's accurate, it can be collected by other means (e.g. via a comment or a contextual attribute like in open-telemetry/oteps#207). the db.query.synthetic would have limited opportunity to evolve into something more usable.

[trask]

I'm 👍 on this

[XSAM]

👍

[trask]

🌟