Server statistics, multi-view record commands, and rc.3 fixes

Added:
- Server statistics: named's memory and CPU (from /proc), cache size,
  sockets and client counts against their limits (statistics channel,
  rndc status), host memory and load, and free disk space. Memory and
  CPU are kept over time as gauges (sum and sample count, averaged in
  timelines). Statistics page Server section, jarl stats server,
  GET /stats/server.
- jarl record add|set|delete|disable|enable --view a,b | all: the same
  change in each view, applied as one changeset.
- Blocking can be paused until resumed (jarl block pause indefinitely,
  "Until I resume", {"indefinitely": true}).

Changed:
- List options (allow-transfer, forwarders, ...) get their braces added
  when given without them.
- The dashboard lists named-checkconf's warnings about the running
  configuration; the CLI prints them after an apply.
- Stats page: tile and card rows fill their width, and the queries and
  failed answers charts share margins so their time axes line up.
- Dashboard: options have their own tile.
- 24-hour times in the web UI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/blocking.md

@@ -168,15 +168,18 @@ most blocked names link to this check.
 
 To see whether blocking is what breaks a site, pause it: every name is
 answered normally until the time is up (at most a day), then blocking
-resumes by itself, also if jarld was restarted in between.
+resumes by itself, also if jarld was restarted in between. A pause can
+also last until someone resumes blocking (like Pi-hole's "indefinitely").
 
 ```sh
 jarl block pause          # 10 minutes; or: jarl block pause 1h
+jarl block pause indefinitely
 jarl block resume         # end it now
 ```
 
-In the web UI, **Pause blocking** is at the top of the Blocking page, and
-the dashboard says while blocking is paused. The lists stay loaded (the
+In the web UI, **Pause blocking** is at the top of the Blocking page (with
+**Until I resume** among the lengths), and the dashboard says while
+blocking is paused. The lists stay loaded (the
 rules zone just lets everything through), so pausing and resuming take
 effect within a second. Pausing and resuming are recorded in the history
 like other changes.