Support for tool_choice parameter for runs

[andehr]

First check

• I added a descriptive title to this issue.
• I used the GitHub search to look for a similar issue and didn't find it.
• I searched the Marvin documentation for this feature.

Describe the current behavior

Apologies if I'm doing this wrong, but I've consulted the documentation and github, and can't find a way to do this so far:

When creating a Run with thread.run(assistant=ai) I'd like to force the assistant to use a specific tool, in this case FileSearchTool.

With the open ai api, that's accomplished with the tool_choice parameter to the create run endpoint: (I think as of April 17th).

You would pass {"type": "file_search"} as its value. Which I think you'd expect to do like this?

thread.run(assistant=ai, tool_choice=FileSearchTool)

But I get a validation error trying that:

pydantic_core._pydantic_core.ValidationError: 1 validation error for Run
tool_choice
  Extra inputs are not permitted

Describe the proposed behavior

If that's not already a feature that I'm missing, then that would be the proposal to force tool use:

thread.run(assistant=ai, tool_choice=FileSearchTool)

Example Use

I find that for some complex examples, forcing a consult with the vector store for each response is worth the latency to ensure each reply is contextful. I think the least impressive bit about the vector store setup is the model's ability to decide when to use it (though yet to test gpt4o much)

Additional context

No response