GeezerVison

Description

AsyncioIntegration currently forks the current scope when a task first runs. If another span becomes current between create_task() and the task's first execution, the task span can end up parented to that unrelated span.

This changes the integration to fork the current scope when the task is created instead. The isolation scope keeps its existing behavior.

The explicit context= path is handled separately so the current scope is taken from the supplied context.

Testing

Added regression coverage for:

• task span parentage when another span becomes current before the task runs
• tasks whose parent span has already ended
• explicit and already-entered context=
• eager task factories
• scope isolation and cancellation behavior

Focused asyncio tests pass on Python 3.8, 3.10, 3.11, 3.12, 3.13, and 3.14.

Also checked:

• ruff
• formatting
• mypy
• compatibility with fix(asyncio): Keep an eager task factory recognizable as eager #7710

Issues

Resolves #7943