dnsmasq owns its resolver format: node-zones is a template, not a controller formatter (ADR 0120)

The node-zones fact was a path; the local=/address= syntax lived in the
control plane. It is dnsmasq's configuration language, so it moves into
dnsmasq's manifest as a template over the roster. The mesh renders it; it
reads none of it. Output is unchanged.

Lands with mesh-controller's ADR 0120 change — the two are one schema step.

modules/dnsmasq/module.json

@@ -70,6 +70,9 @@
     }
   ],
   "facts": {
-    "node-zones": "/etc/mesh-resolver/nodes.conf"
+    "node-zones": {
+      "path": "/etc/mesh-resolver/nodes.conf",
+      "template": "# Generated by the mesh. Do not edit — this file is replaced whenever a machine\n# joins or leaves, and an edit would survive until then and vanish.\n\nlocal=/{{.Suffix}}/\n{{range .Machines}}address=/{{.FQDN}}/{{.Address}}\n{{end}}"
+    }
   }
 }