Add deployment-mode telemetry for App Service and Function Apps

### Summary

Add coherent deployment telemetry for App Service and Function App targets so adoption, duration, and outcomes can be measured by deployment mode.

### Proposed events

- `deploy.appservice.zip` - existing
- `deploy.appservice.container` - new
- `deploy.function.zip` - new
- `deploy.function.container` - new

The spans should cover each target deployment operation and record success/failure through span status. No user-derived attributes are required.

### Motivation

The existing `container.publish` event measures image publishing, not deployment, and can be skipped for prebuilt images. Project-level service target telemetry identifies Function/App Service usage but cannot distinguish zip from container deployments. Instrumenting the complete matrix provides both feature adoption counts and the denominator needed to compare deployment modes without making one target disproportionately observable.

### Required work

- Add the three missing event constants and instrumentation.
- Add focused success/failure span tests.
- Update the public telemetry reference, telemetry schema, and feature-telemetry matrix.
- Complete the telemetry privacy-review checklist and coordinate downstream query/dashboard updates if these events are consumed.

### User impact

No CLI behavior or output changes. Telemetry-enabled users emit an additional anonymous operation span for each applicable deployment; opted-out users remain unaffected.

Related: #9284

Start with the existing deploy.appservice.zip instrumentation and trace the App Service and Function App deployment entry points. Add focused success and failure span tests for the three missing events, then update the public telemetry reference, telemetry schema, feature-telemetry matrix, and privacy-review checklist. Done means the deployment-mode matrix is covered without changing CLI output or opted-out behavior.

Written by the indexing model from the issue text.