Logfire with Celery ingores `token`

If Logfire with Celery throws 'Failed to detach context' errors, update with pip install -U 'logfire[celery]' (logfire 2.7.0 and opentelemetry-instrumentation-celery 0.49b2 are the versions the reporter confirmed fixed it). Also note the docs hook logfire.instrumentcelery() to the workerinit signal, not workerprocessinit.

Source: gh:pydantic/logfire#653 (Pydantic Logfire)

In gh:pydantic/logfire#653, the issue was: ### Description

Hello!

I'm running pytest with Celery (5.4.0) worker in Docker containers without a token and after each task I get the following output:

celery-worker-test-1 | 2024-12-07T11:16:39.350795862Z Traceback (most recent call last):
celery-worker-test-1 | 2024-12-07T11:16:39.350805992Z File "/usr/local/lib/python3.10/site-packages/opentelemetry/context/__init__.py", line 154, in detach
celery-worker-test-1 | 2024-12-07T11:16:39.350810430Z _RUNTIME_CONTEXT.detach(token)
celery-worker-test-1 | 2024-12-07T11:16:39.350814298Z File.... The verified answer: If Logfire with Celery throws 'Failed to detach context' errors, update with pip install -U 'logfire[celery]' (logfire 2.7.0 and opentelemetry-instrumentation-celery 0.49b2 are the versions the reporter confirmed fixed it). Also note the docs hook logfire.instrument_celery() to the worker_init signal, not worker_process_init.. Issue URL: https://github.com/pydantic/logfire/issues/653