Resolve Typing Issues on Wrapping OpenAI Client

[17jmumford]

Details

When wrapping the OpenAI client with the tracker, it set the type as a Union of both the regular and async client. This caused downstream type check errors when using OpenAI classes. TypeVar can resolve this by allowing the output type to match the input type. The IDE will now understand that the type of the client remains the same.

This is the same pattern that currently exists in the Anthropic wrapper.

Issues

Resolves #1152

Testing

Tested locally, fixed the problem. This is my first time contributing, so would love advice/help on what the order of operations is for contributing.

Documentation

No updates to documentation required.

[alexkuzmik]

Good improvement, thanks @17jmumford!

[17jmumford]

Good improvement, thanks @17jmumford!

You're welcome! I'll leave it to you to merge it in. Looks I don't have write access to the repo to hit the merge button. Also sad that the CI checks don't work for me 😢 . Would love to contribute more in the future, lmk what can be done to reduce friction in this process.

[alexkuzmik]

It's a bit tricky with the CI because we have a lot integration tests that require different API keys configured as GitHub secrets.
External contributors do not have access to those secrets(they should configure their own in their repositories), so at first we only look at e2e tests and unit tests, then we might check the integration ones by ourselves.
We'll definitely look into improving the flow in the future to make the process smoothier :)