Add Bring Your Own Observability support to self-managed deployments

Is your feature request related to a problem? Please describe.

Self-managed deployments need a documented path for Bring Your Own Observability (BYOO). BYOO lets operators attach an OpenTelemetry sidecar to each function so end users can configure telemetry providers and export metrics, logs, and traces to their own backends.

This is primarily a multi-tenancy feature: different users or tenants can route function telemetry to the observability systems they own, without requiring all telemetry to flow only into the platform operator's backend.

Describe the solution you'd like

Add BYOO support to the self-managed deployment path.

The implementation should cover:

• OpenTelemetry sidecar injection for each function when BYOO is enabled.
• BYOO collector deployment or documented optional install.
• Required NVCA feature flag and network policy behavior.
• Telemetry provider configuration for metrics, logs, and traces.
• Sample workload validation showing telemetry export end to end.
• Troubleshooting guidance for missing telemetry or blocked egress.

Describe alternatives you've considered

Users can deploy their own observability stack separately or deploy the observability reference architecture, but without BYOO the platform does not provide a tenant-aware path for attaching an OpenTelemetry sidecar to each function and routing metrics, logs, and traces to end user-owned telemetry backends.

Additional context

Suggested acceptance criteria:

• BYOO can be enabled from documented self-managed values.
• NVCA-created resources allow expected BYOO telemetry flow.
• A sample function exports metrics, logs, and traces to a configured user-owned telemetry backend.
• Docs explain required labels, endpoints, telemetry provider configuration, and security considerations.