Use NonRecordingSpan for disabling instrumentation

Is your feature request related to a problem?
Adding excluded URLs for instrumentation does not prevent child span from sending. E.g. we have a health endpoint that checks the DB connection using the "select 1;" query. Adding "health" to excluded URLs removes HTTP span from tracing but DB instrumentation still creates span without root.

Describe the solution you'd like
Disabling instrumentation (e.g. for excluded URLs ) should create NonRecordingSpan instead of not creating span at all.

Describe alternatives you've considered
Implement "suppest instrumentation" key for all instrumentations, but that seems unlikely. This also means that inside the health-check method, we need to add "suppest instrumentation" manually. NonRecordingSpan seems a much better option.

Additional context
We are using aiohttp, flask and fastapi servers and sqlalchemy orm. We are open to contributing if maintainers would accept with feature.

Start by tracing how excluded URLs disable instrumentation in the aiohttp, Flask, and FastAPI integrations, then inspect how SQLAlchemy instrumentation obtains its parent span. Confirm the intended OpenTelemetry behavior for a NonRecordingSpan and identify tests covering excluded URLs. Done means excluded requests provide a non-recording context so child database spans are not exported.