Lengthen the WHOIS fetcher's wait after a skipped lookup (closes #222)

A lookup whose RIR is paused is skipped, and the skip left the fetcher's
wait as it was. Each lookup asks IANA before it finds the RIR paused. So
while most stale ASes were at a paused RIR, the fetcher could ask IANA
every second.

A skipped lookup now makes the wait 1.5 times as long, up to one minute,
as a failure does. It is still not counted as a failure, so the status
page's failure figures leave it out.

Model: opus-5-5

TODO.md

@@ -35,6 +35,11 @@ tested.
 
 # Completed Steps
 
+- 2026-11-02: a WHOIS lookup skipped because its RIR is paused makes the fetcher
+  wait longer before the next lookup, as a failed lookup does, up to one minute.
+  The status page does not count a skip as a failure. A skip used to leave the
+  wait as it was. Each lookup asks IANA first, so while most stale ASes were at
+  a paused RIR, the fetcher could ask IANA every second (closes #222)
 - 2026-11-02: RouteWatch pauses an RIR's or NIC.br's WHOIS server for an hour
   after the server refuses a query. A refused or reset connection is a refusal.
   So is an answer with an `%ERROR:201:` or `%ERROR:202:` line. Lookups at the