Added OTel instrumentation and metrics export for async client

[vladvildanov]

Description of change

This PR provides recording of metrics for async clients. In terms of public API nothing has been changed so you can use #3954 description or official docs to understand the OTel configuration flow.

We only bring new async recorder functions that is used across async clients to collect the same metrics (where it's possible, CSC and SCH are not available via async clients)

Pull Request check-list

Please make sure to review and check all of these items:

• Do tests and lints pass with this change?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

---

Note

Medium Risk
Touches async command execution, retry callbacks, and connection lifecycle paths to emit metrics, which could impact error handling and performance under load. Changes are mostly additive/instrumentation but are in high-traffic code paths (client/cluster/connection/pipeline).

Overview
Adds a new async observability layer (redis.asyncio.observability.recorder) and wires it into asyncio Redis, PubSub, cluster, pipelines/transactions, connection pools, and connection close/health-check paths to record operation durations, errors/retries, pubsub receive events, streaming lag, connection create/wait/close metrics, and geo failover metrics.

Updates async retry to optionally pass a failure count (with_failure_count) and uses it throughout async code to report retry attempts, while also extending sync streaming commands to export lag metrics for both sync and async (wrapping coroutine responses). Adds an async mode to benchmarks/otel_benchmark.py and new/updated asyncio tests validating metric emission and required connection metadata.

^{Written by Cursor Bugbot for commit 0e7d587. This will update automatically on new commits. Configure here.}

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[petyaslavova]

LGTM.
Just check if the cursor comment is valid, and I think it is ready for merging

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}