Deprecate function debuggability

Description

Deprecate and remove the legacy function debuggability surface from NVCF. Define the exact affected APIs, configuration, runtime behavior, and user workflows before removal, and provide a clear migration path for any supported replacement.

Reconcile this work with the profiling and interactive debugging initiatives tracked by #76 and #77 so new workflows do not depend on surfaces scheduled for removal.

Definition of Done

• Inventory affected API endpoints, request and response fields, configuration, permissions, CLI commands, runtime components, and documentation.
• Identify current consumers and define the supported replacement workflow, or explicitly document that there is no replacement.
• Define and publish the deprecation timeline, compatibility window, and removal release.
• Prevent new dependencies on the deprecated surface.
• Provide clear warnings or errors during the compatibility window.
• Migrate existing consumers and ensure existing functions do not retain orphaned debugging state.
• Remove deprecated control-plane, ICMS, NVCA, worker, Helm, RBAC, and CLI integration where applicable.
• Remove obsolete logs, metrics, dashboards, alerts, and documentation without breaking supported observability.
• Add automated coverage for compatibility behavior, migration, authorization, cleanup, and final removal.
• Update customer release notes and operator guidance.

Resources (optional)

• #76
• #77

By submitting this issue, you acknowledge that you are an assigned member of the NVCF development team and agree to follow our code of conduct and our contributing guidelines.

Start by inventorying the affected API endpoints, configuration, permissions, CLI commands, runtime components, Helm and RBAC integration, and documentation. Reconcile the findings with profiling initiative #76 and interactive debugging initiative #77, then define the replacement or no-replacement path, deprecation timeline, compatibility behavior, migration, and final removal coverage.