DB and HTTP semantic convention stability migration for SQLAlchemy

[tammy-baylis-swi]

Description

Add SQLAlchemy instrumentor support for when OTEL_SEMCONV_STABILITY_OPT_IN includes

• "database" or "database/dup"
• "http" or "http/dup"

This changes the SQLComment in span attribute feature if opted in. Inclusion of sqlcomment on query span would be on db.statement and/or db.query.text attribute if default, "database", or "database/dup".

To make the changes cleaner: adds sqlalchemy helper _get_db_name_from_cursor to pull directly instead of having a condition to check attributes taken originally from cursor (see this conversation).

For reusability by other instrumentors later: this PR adds schema url helpers to _semconv.py for choosing the latest appropriate version when an instrumentor uses multiple signal types (http, db, genai).

Adds _set_db_operation to _semconv.py. This adds SQLAlchemy instrumentor setting of db.operation and/or db.operation.name attributes -- this was only done for span name before.

Fixes #2679

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Added unit tests

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[MikeGoldsmith]

Overall looks good 👍🏻

[tammy-baylis-swi]

@open-telemetry/python-maintainers May I get a review please?