Give the zone-file editor something to look at

A textarea holding a master file is a text box: it says nothing about what the
resolver will answer for the zone, and a typo in a record is invisible until a
client sees the wrong answer. `/api/zones` already knows — it is compiled from
the same files — so Local zones now shows the records the daemon has actually
compiled out of the selected file, with the SOA serial and the number of
delegations, above the editor that writes it. It is the same list the Zones
page shows, which is the point: the two pages are two views of one thing, not
two ways of guessing.

The Zones page gains the way back: a zone that comes from a master file rather
than the managed directory has an "Edit the file" button that goes to Local
zones, so a read-only row is a link rather than a dead end.

internal/web/dist/index.html

@@ -5,8 +5,8 @@
     <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <title>web</title>
-    <script type="module" crossorigin src="/assets/index-v8i27mX0.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-DEx0udoi.css">
+    <script type="module" crossorigin src="/assets/index-BFc4v6ED.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-CYPXMp15.css">
   </head>
   <body>
     <div id="root"></div>