Address ranges in address match lists (IPv4 and IPv6)

ACLs, views' match lists, options with address match lists and blocking
client groups take ranges such as 10.0.10.101-10.0.10.199 or
2001:db8::100-2001:db8::1ff (negated, or with spaces around the dash, too).
Jarl stores the range as written and writes the fewest prefixes that cover
exactly that range to named.conf, with the range as a comment. New package
internal/iprange; namedconf gets an AMRange element (a range used to parse
as an ACL name), ExpandRanges and statement comments. Mistakes are refused
when entered, validation sees what ranges cover, and IPv6 ranges in the
IPv4-mapped space get a warning. The web UI shows what a range becomes
while typing (GET /catalog/ranges).

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

docs/blocking.md

@@ -177,8 +177,8 @@ jarl block group list
 In the web UI, the Blocking page's **Devices** panel holds the steps and
 the groups, and each list has a step.
 
-- **Members** are addresses, networks (`10.10.0.0/24`), or ACLs made only
-  of those (`key`, `localnets` and `!` can't be used: blocking matches
+- **Members** are addresses, networks (`10.10.0.0/24`), ranges
+  (`10.10.0.20-10.10.0.49`), or ACLs made only of those (`key`, `localnets` and `!` can't be used: blocking matches
   clients by address). A device is in one group: two groups with the same
   address are refused, but a more specific address in another group wins
   (`10.10.0.0/24` in one group, `10.10.0.20` in another).