[🐛 BUG]: AMQP driver crashes after failing to propagate OTEL headers

[rauanmayemir]

No duplicates 🥲.

• I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?

After upgrading the RR from 2.13.2 to 2023.1.2 my pods started crashing with the following trace:

 net/http/header.go:40
go.opentelemetry.io/otel/propagation.HeaderCarrier.Set(0x1e15faf?, {0x1e14129?, 0xc00058f700?}, {0xc000518180, 0x37})
 go.opentelemetry.io/otel@v1.14.0/propagation/propagation.go:79 +0x97
go.opentelemetry.io/otel/propagation.TraceContext.Inject({}, {0x22a1b88?, 0xc0005968d0?}, {0x22a0ed0, 0x0})
 go.opentelemetry.io/otel@v1.14.0/propagation/trace_context.go:65 +0x41c
go.opentelemetry.io/otel/propagation.compositeTextMapPropagator.Inject(...)
 go.opentelemetry.io/otel@v1.14.0/propagation/propagation.go:117
github.com/roadrunner-server/amqp/v4/amqpjobs.(*Driver).listener.func1()
 github.com/roadrunner-server/amqp/v4@v4.4.7/amqpjobs/listener.go:49 +0x35e
created by github.com/roadrunner-server/amqp/v4/amqpjobs.(*Driver).listener
 github.com/roadrunner-server/amqp/v4@v4.4.7/amqpjobs/listener.go:15 +0x72
panic: assignment to entry in nil map

Version (rr --version)

2023.1.2

How to reproduce the issue?

No way to reproduce as it's only been discovered on high-traffic workloads. It's been working perfectly fine in my test env.

Relevant log output

No response