Added support for passing tool_call_id via the RunContextWrapper

[niv-hertz]

This PR fixes issue: #559

By adding the tool_call_id to the RunContextWrapper prior to calling tools. This gives the ability to access the tool_call_id in the implementation of the tool.

[niv-hertz]

@rm-openai - This addressed the issue we discussed in another thread, would love you review :)

[rm-openai]

Sorry for delayed review. Was thinking about it, and it feels a bit bad to have tool_call_id be nullable.

What if instead we had ToolContext subclass RunContextWrapper. That way, existing usecases would just work since the downcast is fine. And tool_call_id would be non-null always?

[niv-hertz]

Sorry for delayed review. Was thinking about it, and it feels a bit bad to have tool_call_id be nullable.

What if instead we had ToolContext subclass RunContextWrapper. That way, existing usecases would just work since the downcast is fine. And tool_call_id would be non-null always?

@rm-openai - I added a ToolContext object such that new users will be able to create tool functions that receive the ToolContext instead of the AgentContextWrapper. I also modified the internal FunctionTool class to only receive the ToolContext object in the on_invoke_tool params, so this change will break the type checking of anyone who uses the FunctionTool class directly instead of the wrappers. It seemed reasonable to me, let me know if you think otherwise.

[niv-hertz]

@rm-openai - bumping this 😄

[rm-openai]

Looks good, please just fix the typecheck etc and I can merge

[rm-openai]

awesome thanks for implementing this!