Increase the log level for potential ThreadLocal leaks

[jhsbeat]

Is your feature request related to a problem? Please describe.
We've observed some ThreadLocal leaks due to the unclosed scope or close attempts in wrong order.
It makes really hard to figure out the cause when it works with opentelemetry java instrumentation because it's working as a shaded dependency and the log message level if FINE.
It's hard to implement a custom context storage when it comes with java instrumentation.

Describe the solution you'd like
I hope that it can be log the wrong attempts of closing the scope as ERROR or WARN level at least.

• opentelemetry-java/context/src/main/java/io/opentelemetry/context/ThreadLocalContextStorage.java

  Line 53 in ddc9c91

  Level.FINE,

Describe alternatives you've considered
N?A

Additional context
N/A

[trask]

It makes really hard to figure out the cause when it works with opentelemetry java instrumentation because it's working as a shaded dependency

Have you tried -Dio.opentelemetry.javaagent.shaded.io.opentelemetry.context.enableStrictContext=true?

E.g. https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/e12ae9742b322f2e022843499687b6a9aa17ae5f/conventions/src/main/kotlin/otel.java-conventions.gradle.kts#L347