fix: OpenTelemetry bugfixes

[evansims]

Description

This PR fixes several bugs identified in the recent OpenTelemetry improvements:

• Fixed http_client_request_duration being reported in seconds rather than the intended milliseconds
• Fixed the sync client mistakenly passing the entire configuration (rather than just the OpenTelemetry configuration as intended) to queryDuration() and requestDuration().
• Fixed an issue in which some attributes may not have been exported as expected under some conditions
• All attribute values are now correctly exported as their intended types rather than defaulting to strings
• Fixed an issue in which queryDuration() and requestDuration() may not have updated their histograms reliably when attr_http_client_request_duration or attr_http_server_request_duration (respectively) were not enabled (which is the default)

References

Review Checklist

• [x] I have clicked on "allow edits by maintainers".
• [ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
• [x] The correct base branch is being used, if not main
• [ ] I have added tests to validate that the change in functionality is working as expected

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 63.46154% with 19 lines in your changes missing coverage. Please review.

Project coverage is 69.16%. Comparing base (4ecb08f) to head (b3225c0).

Files with missing lines	Patch %	Lines
openfga_sdk/telemetry/attributes.py	67.74%	10 Missing :warning:
openfga_sdk/telemetry/metrics.py	57.14%	9 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #124 +/- ## ========================================== + Coverage 69.14% 69.16% +0.01% ========================================== Files 121 121 Lines 9941 9982 +41 ========================================== + Hits 6874 6904 +30 - Misses 3067 3078 +11 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[evansims]

Can you also please:

• Update the documentation page with

  1. the defaults
  2. How to configure it
• Update the example with a sample configuration?
• Add validation that they're not configuring with invalid meter/attribute names?

I'd prefer to do a documentation pass as a separate PR, but yup, that's on my radar.

Right now providing an invalid meter/attribute would just be ignored; I can add an exception for those instances. Updated the PR with that; added a test to cover it