Make agent creation swarm-only and refuse a name placed on another hive

swarm-controller's POST /api/agents now refuses (409) a name the swarm
has already placed on a different hive: a non-Destroyed declaration in
that hive's wanted state, or a SetAgentWanted node still queued for it.
The same name on the same hive is that agent being re-created and goes
through. A wanted state that cannot be read refuses (503/500) instead of
reading as "placed nowhere". Creations are serialised from that read to
the graph insert so two concurrent creations of one name cannot both
pass.

Hive-level creation is removed: hivectl `agent create` / `request-create`,
HostRequest::Spawn / RequestSpawn, the dashboard POST /api/request-spawn
route, and ApprovalKind::Spawn with its approve/resolve arms and the
approval-carrying `templates::spawn`. The swarm path (deploy request or
wanted-state sweep -> queue_first_deploy -> templates::first_deploy) used
none of them. Old `spawn` approval rows are skipped by collect_lenient,
as `init_config` rows were in a3b672d1.

policy.rs's comment on agent_object_name stated swarm-wide name
uniqueness as a fact; it now says where it is enforced and what that
check cannot see.

Refs #4396

docs/scheduler/coordinator.md

@@ -322,7 +322,7 @@ the build slot while its parent held the meta window could block waiting for
 a resource its own parent already committed to, a lock-ordering hazard that
 one multi-resource root avoids by construction.
 
-`Spawn` and `UpdateMetaInputs` approvals map onto the ordinary `spawn` /
+`UpdateMetaInputs` approvals map onto the ordinary
 `meta-update` shapes. The scheduler fires `actions::resolve_approval_dag`
 exactly once when **any** approval-carrying DAG settles terminal — deploys
 included, since their outcome is now the DAG's own state (including