feat(events): record a created deployment with the uuid it was given (#7115)

`Create Crew Deployment` fires before the API call that creates the
deployment, so it counts creation ATTEMPTS and cannot carry the uuid - the
call that creates the deployment is the call that returns it. Live effect:
`create_deployment` reads 76,015 events with 0 carrying a uuid (0.000%), so
deployments cannot be joined to anything.

Moving the existing span after the response would fix the uuid and silently
redefine the metric, turning attempts into successes; the deployment churn
figures are built on attempts. So this adds a second span rather than moving
the first.

`Crew Deployment Created` fires after `_validate_response`, which raises
SystemExit on failure - a failed create therefore still counts as an attempt
and reports no creation. Both creation paths, git remote and zip upload,
converge on that line and both return the uuid.

Emits no `deploy:created` feature count: the attempt span already does, and a
second emit would double the deployment count that origin-independent
aggregation depends on.

Tests cover the emitter (uuid carried, distinct span name, no second feature
count, absent-vs-empty uuid) and the call site across both creation paths plus
the failure path.

The warehouse consumer must be widened BEFORE this merges or it delivers
nothing: `mv_span_fanout_forward` filters on a hard-coded 13-name allowlist,
and `mv_fanout_deployment_spans`'s `multiIf` ends in a catch-all `remove_crew`
arm that would mislabel the new span. Runbook prepared separately.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

lib/cli/src/crewai_cli/deploy/main.py

@@ -375,7 +375,16 @@ class DeployCommand(BaseCommand, PlusAPIMixin):
             response = self._create_crew_from_zip(env_vars, repository, confirm)
 
         self._validate_response(response)
-        self._display_creation_success(response.json())
+        json_response = response.json()
+        # After _validate_response, not before: it raises SystemExit on a failed
+        # create, so the span cannot fire for a deployment that was not made. This
+        # is the first point at which the uuid exists -- the pre-flight span at the
+        # top of this method counts the attempt and cannot carry it.
+        created_uuid = json_response.get("uuid")
+        self._telemetry.crew_deployment_created_span(
+            uuid=str(created_uuid) if created_uuid else None, source=source
+        )
+        self._display_creation_success(json_response)
 
     def _prepare_git_repository(self) -> git.Repository | None:
         """Prepare Git for deploy while preserving remote deploy when possible."""