feat: add resp format, timeout, model override to conversation api

[sicoyle]

Description

This PR adds:

• timeout support for llm providers on the http client and to prevent idle connections from being closed
• response format field - this is something that users rely on. In dapr agents we do a workaround for this that I want to rm with this addition
• i also had to bump langchain versions for some of the new options to be supported (even with the workarounds)
• conversation api model override parameter bubbled over and returned in the response

API PR: dapr/dapr#9241

I need this PR merged first to then merge my dapr/dapr one.

I tested conformance test on: mistral, openai, anthropic.
I have a few fixes left for ollama, and aws (this one was broken to begin with...).

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation
  • Created the dapr/docs PR:

Note: We expect contributors to open a corresponding documentation PR in the dapr/docs repository. As the implementer, you are the best person to document your work! Implementation PRs will not be merged until the documentation PR is opened and ready for review.

[CasperGN]

@sicoyle does this (or the linked pr) also carry bubbling out the model, tokens etc into the metadata api like we discussed?

[sicoyle]

@sicoyle does this (or the linked pr) also carry bubbling out the model, tokens etc into the metadata api like we discussed?

The model was the only thing that I can remember that we want bubbled out into the metadata api. I can look to PR that later today or tomorrow :)

[sicoyle]

The “from metadata” fields were bubbling the Metadata field from the Conversations API (see https://github.com/dapr/dapr/blob/master/dapr/proto/runtime/v1/ai.proto#L43
), which allowed all of these fields to be passed through the request. This is an incorrect use of metadata. Components already expose their own metadata field, so there’s no need to bubble this information up from the API—contrib already handles it.

As a result, we can remove the following fields: Key, Endpoints, and Policy.

I also removed Parameters and ConversationContext, since these were surfaced but never actually used. All of this traces back to the original implementation, which I’m now cleaning up.

[sicoyle]

ready for feedback please @cicoyle and @JoshVanL 🙏

[sicoyle]

ignore this please as I am WIP splitting this into different PRs