Fix span context manager typing by using ParamSpec from typing_extensions

[aabmass]

Description

Span context manager functions that use the _agnosticcontextmanager decorator (like start_as_current_span()) are currently of type Unknown when type checking for python <3.10 with pyright. This was coming up in open-telemetry/opentelemetry-python-contrib#3192 (failed run).

Also Fix #3836

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?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Type checking passed on Added Vertex AI spans for request parameters opentelemetry-python-contrib#3192

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated

[emdneto]

There is an issue I think is related and this PR also fix it: #3836

[tool.pyright]
pythonVersion = "3.8"

from opentelemetry import trace

tracer = trace.get_tracer(__name__)

with tracer.start_as_current_span(name="foo"):
    print("Hello world!")

With this pyright config and running the example against main, results in this error ❌ :

(main) $ pyright example.py 
/workspaces/opentelemetry-python/example.py
  /workspaces/opentelemetry-python/example.py:5:35 - error: No parameter named "name" (reportCallIssue)
1 error, 0 warnings, 0 informations 

Running against this branch results in ✅ :

(agnostic-type-fix) $ pyright example.py 
0 errors, 0 warnings, 0 informations 

[aabmass]

Running against this branch results in ✅ :

Yup looks like the same issue 👍