Describe the bug

My java service takes a hit in terms of latency when adding opentelemetry. It works correctly without Otel.

Below versions are used:
lettuce : 6.1.10
reactor-core : 3.5.3

Only this exception is being printed in application logs :

throwIfFatal detected a jvm fatal exception, which is thrown and logged below:
java.lang.NoSuchMethodError: reactor.core.publisher.Mono.subscriberContext()Lreactor/core/publisher/Mono;
	at io.lettuce.core.tracing.Tracing.getContext(Tracing.java:84) ~[lettuce-core-6.1.10.RELEASE.jar!/:6.1.10.RELEASE]

Adding otel autoinstrumentation using the startup args in the java service.

Steps to reproduce

1. Use lettuce with reactor-core and call redis operations.
2. This should cause lot of exceptions and takes a hit for my api latency and errors

Expected behavior

No exceptions

Actual behavior

throwIfFatal detected a jvm fatal exception, which is thrown and logged below:
java.lang.NoSuchMethodError: reactor.core.publisher.Mono.subscriberContext()Lreactor/core/publisher/Mono;
	at io.lettuce.core.tracing.Tracing.getContext(Tracing.java:84) ~[lettuce-core-6.1.10.RELEASE.jar!/:6.1.10.RELEASE]

Javaagent or library instrumentation version

java sdk : 2.2.0

Environment

JDK:
OS:

Additional context

No response