DB semantic convention stability migration for DB-API and 7 inheriting db client instrumentors

[tammy-baylis-swi]

Description

Add DB-API instrumentor support for when OTEL_SEMCONV_STABILITY_OPT_IN includes "database" or "database/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".

These instrumentors inherit DB-API's wrap_connect and/or instrument_connection, and therefore also gain support for semconv migration automatically:

1. mysql
2. mysqlclient
3. psycopg2
4. psycopg
5. pymssql
6. pymysql
7. sqlite3

Fixes #2929 #2678 #2928 #2931 #2932 #2933 #2934

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

[tammy-baylis-swi]

Not sure why A failure started happening in this PR instead of in #4108 with tox -e py3*-test-opentelemetry-instrumentation-aiopg because of aiopg instrumentor dependency on this. Example run with error:

TypeError: int() argument must be a string, a bytes-like object or a real number, not 'Mock'