Expose additional metadata that's currently internal/private

[stephentoub]

Confirm this is not a feature request for the underlying OpenAI API.

• This is not a feature request for the underlying OpenAI API

Confirm this is not a feature request for Azure OpenAI.

• This is not a feature request for Azure OpenAI

Describe the feature or improvement you're requesting

• OpenAIClient should expose Url Endpoint { get; }
• ChatClient should expose string Model { get; }
• Clients like ChatClient should expose a way to navigate back to the owning OpenAIClient so that if you have access to the ChatClient, you can access its Endpoint, or alternatively the Endpoint should also be exposed on ChatClient.

Additional context

No response

[jsquire]

@KrzysztofCwalina, @christothes: This one has been sitting for a bit. Would appreciate your thoughts on whether this is a request that should move forward, or we feel is not aligned with the design.

[christothes]

Model was recently added to many of the clients in this PR - I'll defer to @KrzysztofCwalina on the plan for exposing Endpoint.

[KrzysztofCwalina]

We should expose Endpoint too. @joseharriaga had some concerns about it, but I think we talked it through and decided that we can expose.

[jnssksk]

Exposed Endpoint would be great.
Not being able to override it is blocking me from using Extensions.Ai.OpenAi for 2 different tools currently

[stephentoub]

Addressed in 2.4.0. Thanks!