refactor(#2754): make the container weights Option, not a 0 sentinel

Encoding "not configured" as weight 0 worked (the writer omitted the
line) but the type lied: 0 is not a legal cgroup v2 weight, and every
reader had to know the sentinel. Use Option<u32> end to end instead —
wire type, priv_client, HiveEnv, drop-in writer — so "unset" is a state
of the type rather than a magic value.

The nix options become nullOr, keeping their default of 80; null now
expresses "leave the setting out of the drop-in entirely" declaratively,
which is the useful shape on a host whose IO scheduler ignores
io.weight anyway.

Backward compat is unchanged: the fields stay #[serde(default)], so a
request from an older hive-c0re deserialises to None and reproduces the
pre-weights drop-in byte for byte. The test that pins that now passes
None instead of 0.

hive-c0re/src/lifecycle/host_config.rs

@@ -45,12 +45,14 @@ pub async fn write_dropins(name: &str, hive: &HiveEnv, paths: &AgentPaths) -> Re
 /// The weights are hive-wide (`services.hyperhive.agentCpuWeight` /
 /// `agentIoWeight`) — unlike the caps they have no per-agent override in
 /// `meta/resource-limits.json`, so they come straight off [`HiveEnv`].
+/// `None` (the nix option set to `null`) means the weight line is left out
+/// and the container keeps the kernel default.
 async fn set_resource_limits(
     container: &str,
     cpu_quota: &str,
     memory_max: &str,
-    cpu_weight: u32,
-    io_weight: u32,
+    cpu_weight: Option<u32>,
+    io_weight: Option<u32>,
 ) -> Result<()> {
     crate::priv_client::write_resource_limits(
         container, memory_max, cpu_quota, cpu_weight, io_weight,