No spans in APM when transaction is active

Hello! I have tried to use master branch to connect the dots in async background tasks (using the `elasticapm.get_client`)

Here is my "stack"
```

+-------------------+
| Backend Service |
| |
| with APM Agent |
+---------|---------+
| TraceParent is passed if request originated
| from another APM Agent, otherwise transaction is created
| and TraceParent is created and passed
+-------------------+
| uWSGI Spooler |
| Task Queue |
| (Async) |
+-------------------+
| Transaction is active, visible and connected in APM,
| however SPANs to this transactions are not visible anywhere
+---------|---------+
| Asynchronnous | -
| Background |
| Task |
+-------------------+

```

This somehow works, and I can see the whole transaction in APM even though the request only submits the tasks to queue and returns immidately after few miliseconds, so it is correctly paired with the trace id.


However inside the task, which has this transaction active, I am creating spans with `elasticapm.capture_span` decorator, and they are not visible in APM. I've added logging to really double check that there is indeed a valid active transaction.

simplified codeblock:
```python
logger.info(f"Transaction before caputuring span: {elasticapm.get_transaction_id()}")
with elasticapm.capture_span("my_span"):
do_stuff()
```

Which returns:
```
[info] Transaction before caputuring span: 44d90007a40c8780
```

That matches the transaction that I can see in APM:

But I do not see the spans in APM, what am I doing wrong?

Start with the reported Python entry points, elasticapm.get_client and elasticapm.capture_span, and reproduce the uWSGI Spooler path using the simplified example. Trace how the active transaction and captured span are handled in the asynchronous task; done means the span is visible in APM under the transaction shown in the report.

Escrito por el modelo de indexación a partir del texto del issue.