chore: sync deployment-operator CRDs

[github-actions]

Automated pull request to sync deployment-operator CRDs from console.

[greptile-apps]

Greptile Summary

This automated sync updates the chart’s bundled CRDs to match the current generated Console definitions.

• Adds the AgentRuntime.spec.mcpServers schema, including remote server, header-source, list, and validation contracts.
• Refreshes embedded Kubernetes workload schemas in AgentRuntime and PipelineGate.
• Reorders existing AgentRun and AgentRuntime fields and updates generated descriptions without changing their validation contracts.

Confidence Score: 5/5

The PR appears safe to merge because no concrete changed-code failure was identified.

The synchronized CRDs preserve existing public field requirements while adding a structurally defined MCP server capability and refreshing generated Kubernetes schemas consistently across affected resources.

Important Files Changed

Filename	Overview
charts/deployment-operator/crds/deployments.plural.sh_agentconfigurations.yaml	Updates the description of componentShaCacheTTL without changing its schema.
charts/deployment-operator/crds/deployments.plural.sh_agentruns.yaml	Reorders the existing branch property and refreshes deprecated-field formatting without changing validation.
charts/deployment-operator/crds/deployments.plural.sh_agentruntimes.yaml	Adds the remote MCP server contract and refreshes generated embedded Kubernetes schemas; no concrete defect was identified.
charts/deployment-operator/crds/deployments.plural.sh_pipelinegates.yaml	Refreshes the embedded Job and Pod schemas without changing the PipelineGate identity, required fields, or status contract.

_{Reviews (1): Last reviewed commit: "chore: sync deployment-operator CRDs" | Re-trigger Greptile}