Use FastThreadLocal for context propagation if available

[yawkat]

From #10131

[dstepanov]

Can we have an abstraction around the thread context and only switch to Netty's implementation when it's available (server/client)?

[yawkat]

I don't understand what you mean? If netty is not on the classpath, the SLOW variable will be used. If netty is on the classpath but the current thread is not a netty FastThreadLocalThread, then netty FastThreadLocal has its own handling already that falls back on ThreadLocal.

[dstepanov]

Ah right, I didn't notice compileOnly

[sonarqubecloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

1 New issue
0 Security Hotspots
95.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud