Use standard JSON Schema format for VMCP composite tool parameters

[JAORMX]

Fixes #2650
Fixes #2775

Summary

Changes composite tool parameter definitions to use standard JSON Schema format per the MCP specification, instead of a non-standard simplified format.

This also resolves the field mismatch between ParameterSpec (CRD) and ParameterSchema (implementation) documented in #2775. By moving to standard JSON Schema format with map[string]any, all JSON Schema fields (description, required, default, etc.) are now supported automatically without needing separate struct fields.

Large PR Justification

This PR exceeds 1000 lines due to the combination of:

1. Breaking schema format change - Migrating from a custom parameter format to standard JSON Schema requires updating multiple layers (CRDs, config types, converters, yaml loaders)
2. Comprehensive test coverage - Added extensive tests to verify the new JSON Schema format works end-to-end, including explicit test cases for issue Align ParameterSpec and ParameterSchema fields between CRD and implementation #2775 (verifying description, default, required field preservation)
3. Documentation updates - Multiple docs needed updates to reflect the new schema format
4. Generated code - CRD changes require regenerating deepcopy functions and manifests

The changes are tightly coupled and cannot be safely split - a partial migration would leave the system in an inconsistent state where some components expect the old format and others expect JSON Schema.

Breaking Change

Composite tool parameter format has changed from:

parameters: param1: type: "string" default: "value"

To standard JSON Schema:

parameters: type: object properties: param1: type: string description: "Parameter description" default: "value" required: ["param1"]

Changes

• Update CompositeToolConfig.Parameters to map[string]any (full JSON Schema)
• Remove ParameterSchema struct from implementation (fixes Align ParameterSpec and ParameterSchema fields between CRD and implementation #2775)
• Remove ParameterSpec type from CRD, replaced with runtime.RawExtension
• Remove parameter transformation logic from yaml_loader and workflow_converter
• Add JSON Schema validation in yaml_loader (checks type: object)
• Update Kubernetes CRDs to use runtime.RawExtension for parameters
• Update webhook validation to handle runtime.RawExtension
• Regenerate CRD manifests and deepcopy code
• Bump operator-crds Helm chart from 0.0.59 to 0.0.60
• Update all tests and documentation
• Add converter test cases verifying Align ParameterSpec and ParameterSchema fields between CRD and implementation #2775 fields are preserved
• Add capability adapter test verifying fields reach MCP clients

Test plan

• All existing tests pass
• Linting passes (0 issues)
• Updated tests to use new JSON Schema format
• Validated error messages match new validation logic
• Added test case verifying description and default fields preservation (issue Align ParameterSpec and ParameterSchema fields between CRD and implementation #2775)
• Added end-to-end test verifying fields are exposed to MCP clients

🤖 Generated with Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 15 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.45%. Comparing base (4e36464) to head (e32b8d4).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/vmcp/config/yaml_loader.go	65.21%	5 Missing and 3 partials ⚠️
...lpha1/virtualmcpcompositetooldefinition_webhook.go	46.15%	3 Missing and 4 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@ ## main #2651 +/- ## ========================================== + Coverage 56.34% 56.45% +0.11%  ========================================== Files 319 319 Lines 30887 30878 -9 ========================================== + Hits 17402 17431 +29  + Misses 11999 11948 -51  - Partials 1486 1499 +13 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jhrozek]

Looking good! I added some nits. Only because I was reviewing the docs earlier this week do I know that we in fact have docs (docs/operator/advanced-workflow-patterns.md and docs/operator/virtualmcpcompositetooldefinition-guide.md) that @tgrunnagle wrote, thos should probably be updated as well

[tgrunnagle]

Couple of questions but non-blocking

[JAORMX]

Thanks for the review @tgrunnagle!

Regarding your questions:

Strong typing for Parameters (config.go)
We use map[string]any rather than a typed struct because JSON Schema is highly flexible with many optional fields (default, enum, minimum, maximum, pattern, items, additionalProperties, oneOf, anyOf, allOf, etc.). Using map[string]any allows full JSON Schema compatibility without needing to define every possible field, and matches how the MCP SDK handles inputSchema. I've added a code comment explaining this rationale.

Non-object top level parameters (yaml_loader.go)
We enforce type="object" because MCP tools use named parameters (inputSchema.properties), and non-object types (e.g., type="string") would mean a tool takes a single unnamed value, which doesn't align with how MCP tool arguments work. The MCP SDK and specification expect tools to have named parameters accessible via inputSchema.properties. I've added a code comment explaining this as well.

[github-actions]

Large PR Detected

This PR exceeds 1000 lines of changes and requires justification before it can be reviewed.

How to unblock this PR:

Add a section to your PR description with the following format:

## Large PR Justification [Explain why this PR must be large, such as:] - Generated code that cannot be split - Large refactoring that must be atomic - Multiple related changes that would break if separated - Migration or data transformation

Alternative:

Consider splitting this PR into smaller, focused changes (< 1000 lines each) for easier review and reduced risk.

See our Contributing Guidelines for more details.

---

This review will be automatically dismissed once you add the justification section.

it's no longer as big as it used to be