Use TracerProvider and MeterProvider instead of Tracer and Meter

[iRevive]

Motivation

OpenTelemetry recommends libraries to own their instrumentation scopes.
A few benefits:

1. Full control of the namespace - the traces & metrics will belong to the org.typelevel.skunk - which simplifies the filtering
2. Every release will be reflected in the instrumentation scope version - much easier to spot regressions and filter traces/metrics if needed

---

https://opentelemetry.io/docs/concepts/instrumentation-scope/

For libraries and frameworks: use the library’s fully qualified name and version as the scope. If you are writing an instrumentation library for a library that has no built-in OpenTelemetry support, use the name and version of the instrumentation library itself.

[iRevive]

Second step: introduce a proper Telemetry abstraction, where we can unify all telemetry ops: internal/db/pool traces, metrics, and so on.

[iRevive]

If we want to keep it, we need to change the signature to:

def singleF[F[_]: Temporal: Network: Console](
  ...
): Telemetry[F] => Resource[F, Session[F]]

[iRevive]

Hm, I'm starting to think the update step is not necessary, since other branches somehow work 🤔