Don't count a per-view counter going down as a restart of named

After a reconfig that changed named's views, the cache and resolver
counters (summed over views) went down, which was taken for a restart:
every counter then counted its total since named started for one minute.
Only a new boot time means a restart now; a counter that goes down
counts 0.

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

CHANGELOG.md

@@ -66,6 +66,12 @@ All notable changes to Jarl are documented here. The format follows
 
 ### Fixed
 
+- Statistics: after a reconfig that added, removed or recreated views
+  (creating the first view, for instance), a minute could count everything
+  since named started: millions of queries in an hour. A per-view counter
+  (cache, upstream times, validation) going down was taken for a restart
+  of named. Now only a new boot time means a restart, and a counter that
+  goes down counts 0 for that minute.
 - Blocking page, checking a name: when your own block rule is for that very
   name, it offers to remove the rule instead of an allow rule, which was
   refused as a second rule for the same name. It also names the rule that