Bug: No telemetry recorded for failed requests

Summary

In src/main/java/dev/openfga/sdk/api/client/HttpRequestAttempt.java, when a request fails permanently (max retries exceeded, non-retryable error), requestDuration and queryDuration metrics are never recorded. Only the success path (~line 211-221) records metrics.

Impact

• Error rates are invisible via telemetry
• Request duration for failed calls is not tracked
• Users cannot build alerting/dashboards on error patterns
• Failed requests are a silent gap in observability

Proposed Fix

Record requestDuration on all terminal paths (success and failure), not just success. The http.response.status_code attribute already distinguishes success from failure, so existing dashboards filtering by status code will continue to work correctly.

This could be done with a try/finally pattern or by recording metrics just before throwing in the error paths.

Related

• PR #290 (telemetry instance sharing fix)

Start in src/main/java/dev/openfga/sdk/api/client/HttpRequestAttempt.java, focusing on the success-path metric recording around lines 211-221 and the terminal failure paths for exhausted retries and non-retryable errors. Ensure requestDuration and queryDuration are recorded for failed requests as well as successful ones, while preserving the existing status-code distinction.