Add otel4s-instrumentation module

[iRevive]

This module specifically targets the OpenTelemetry instrumentation module. However, it works without IOLocal propagation, which can incur a notable performance penalty.

Usage example: iRevive/otel4s-showcase#6.

[iRevive]

That's the main trick: we explicitly activate context when running primitive operations.

So JdbcTelemetry instrumentation runs in the correct context, and the spans are correctly connected.

[mzuehlke]

Super simple.
Maybe this even makes it easier to connect errors to the correct origin.
Sometime / often in doobie the stacktraces contain no connection to the application code.

[iRevive]

@mzuehlke while #2385 looks good, this functionality is surprisingly straightforward.

The classpath pollution is also minimal:
https://mvnrepository.com/artifact/io.opentelemetry.instrumentation/opentelemetry-jdbc/2.25.0-alpha/dependencies

[iRevive]

I still don't like the fact that we need to include the alpha dependency in the classpath. Perhaps it would be enough to document this, and users can replicate the code in their codebases?

However, I find the new fragment syntax (i.e., queryWithSummary) quite useful, and it will not work with this instrumentation out of the box. But with a few tricks, it can be doable, I think.