feat: Add custom span naming for dbapi and requests

[bhushan-amit]

Description

This pull request contains custom modifications to the opentelemetry-instrumentation-dbapi and opentelemetry-instrumentation-requests packages. The primary goal of these changes is to enrich the default span names for database and HTTP client operations with more specific, low-cardinality information.

• For dbapi instrumentation: The span name is modified to include the table name, derived from parsing the SQL statement. For example, a span for SELECT * FROM users will be named SELECT users.
• For requests instrumentation: The span name is modified to include the URL path. For example, a span for a GET request to https://example.com/api/v1/users will be named GET /api/v1/users.

Note: This pull request is for internal use and serves as a proof of concept. The changes bypass standard extension points and would not be suitable for general use. We are using this fork to deploy our custom instrumentation packages via a git dependency in our requirements.txt.

No issue is fixed in the upstream repository, as this addresses a specific configuration challenge we encountered.

Type of change

• 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?

This change was tested in a local Dockerized Python 3.11 environment.

• Test 1: Psycopg2 Span Naming
  • A simple Python script was created to connect to a PostgreSQL database via psycopg2 and execute a DML query (e.g., SELECT, INSERT).
  • The generated traces were observed to verify that the database spans had names in the format {OPERATION} {table_name}.
• Test 2: Requests Span Naming
  • A Python script was created to make an HTTP GET request using the requests library to a specific URL (e.g., http://example.com/users/123).
  • The generated traces were observed to verify that the HTTP client spans had names in the format {METHOD} {url_path}.

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

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

[linux-foundation-easycla]

• ❌ The email address for the commit (6132d94, e0d372c, f684cf7, 04ec423, aa2df3b) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.