fix(toolbox-core): Expose authorization token requirements on ToolboxTool

[anubhav756]

Summary

This PR exposes the authorization token requirements from the ToolboxTool class by promoting the internal list of required authorization tokens to a read-only property.

Motivation

Currently, the list of authorization services that a tool requires is stored as a private attribute within the ToolboxTool instance. This encapsulation makes it difficult for external wrapper classes or orchestration layers to programmatically inspect a tool and determine its authentication needs.

The ultimate goal, which will be implemented in a future PR (#291), is to enable self-authenticated tools. This feature requires the ability for toolbox-langchain wrapper to introspect a tool instance, identify its authorization requirements, and potentially manage the token acquisition lifecycle automatically. Currently we only expose authentication requirements, that is a map of parameter names to the corresponding applicable authentication services.

This PR is the necessary first step, providing a clean and stable public API to access this information.

Changes Proposed

• A new read-only public property, required_authz_tokens, has been added to the ToolboxTool class.
• This property returns an immutable tuple of the authorization service names (e.g., ('my-auth-service', 'another-service')) required by the tool.
• By exposing this as a property, we establish a clear contract for consumers of the ToolboxTool core class, avoiding the need to access private (__ToolboxTool_) attributes.

Note

This change is non-breaking and purely additive.

[anubhav756]

/gcbrun