feat(triggers): surface name on the Trigger model (§4.5, step B-1)

Read the new `name` column through the data model: `Trigger`/`TriggerRow`
carry it, every trigger SELECT/RETURNING includes it, and the row→Trigger
assembly + the interactive create paths populate it (the create INSERTs
still omit it, so they take the migration's default). Behavior unchanged
— the apply diff still keys on the semantic tuple; B-2 switches it to
name-keying (enabling Update) and wires the manifest.

Tested: manager-core lib 367 + trigger journeys green; clippy clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

crates/manager-core/src/apply_service.rs

@@ -1445,7 +1445,13 @@ fn disabled_target_warnings(bundle: &Bundle) -> Vec<String> {
         if r.enabled && disabled.contains(r.script.as_str()) {
             out.push(format!(
                 "route `{}` is enabled but its script `{}` is disabled — it will 404",
-                route_key(r.method.as_deref(), r.host_kind, &r.host, r.path_kind, &r.path),
+                route_key(
+                    r.method.as_deref(),
+                    r.host_kind,
+                    &r.host,
+                    r.path_kind,
+                    &r.path
+                ),
                 r.script
             ));
         }
@@ -1919,6 +1925,7 @@ mod tests {
             id: TriggerId::from(uuid::Uuid::new_v4()),
             app_id: AppId::from(uuid::Uuid::nil()),
             script_id,
+            name: "t".into(),
             kind,
             enabled: true,
             dispatch_mode: TriggerDispatchMode::Async,