feat: prune bound parameters from exposed tool definition

[stenalpjolly]

Summary

This PR implements bound parameter pruning from the exposed tool definition. When parameters are bound to a value or a dynamic supplier, they are resolved by the client, so they are removed from the exposed ToolDefinition that is returned to the user or LLM.

Expectation & Implementation

• Refactored the Tool class to be immutable, making all configurations return a new Tool instance with the updated state.
• Inside bindParam, we clone the current ToolDefinition and filter out the bound parameter name from the parameter list.
• Adjusted tool loading loops in McpToolboxClientImpl to support the new immutable Tool pattern.
• Updated example and demo controllers (ExampleUsage.java and CymbalTransitController.java) to chain or capture the return values of bindParam calls.

Test cases

• Run the JUnit test suite to verify everything compiles and passes:
  mvn test -Dtest="*Test,!*E2ETest" -Dnet.bytebuddy.experimental=true
• Verification of new JUnit test testBoundParameterPruning confirming that:
  • Statically and dynamically bound parameters are correctly pruned from the exposed tool definition list.
  • The client execution still correctly receives the bound parameter values.
  • Verification with null parameter definitions behaves correctly without throwing exceptions.

Acceptance criteria

• Line coverage for Tool.java and McpToolboxClientImpl.java remains at 100.00%.
• Checked and passed Checkstyle build check with 0 violations.

Breaking changes

None.