Adopt structured error data field in ToolCallException

[kornys]

Summary

Evaluate and adopt the optional data field added to McpException/McpError in 2.0 for structured error details.

Currently @WrapBusinessError wraps exceptions as plain text messages. Structured error data (resource name, namespace, error category) could help LLM clients handle
errors more intelligently.

Scope

• Check if ToolCallException constructor supports a data field
• Identify key error paths that would benefit from structured context
• Update error handling in tool classes if beneficial

Acceptance criteria

• API evaluated
• Key error paths updated if beneficial
• CHANGELOG.md updated