Read only the AS's objects in RIPE, APNIC and AFRINIC answers (closes #168)

APNIC and RIPE start their answer for an AS with the as-block object of
the block the AS is in. The parser kept the first value of each field
across the whole answer, so it stored the block's dates as the AS's.

The parser now reads an answer from RIPE, APNIC or AFRINIC object by
object. It takes the fields from the aut-num object and the organisation
object it names, and leaves out every other object. The irt object's
address therefore no longer joins the organisation's. ARIN and LACNIC
answers are parsed as before.

Model: opus-5-5

TODO.md

@@ -33,6 +33,10 @@ tested.
 
 # Completed Steps
 
+- 2026-10-27: the WHOIS details of an AS at RIPE, APNIC or AFRINIC come only
+  from its `aut-num` object and the organisation object it names. RIPE and APNIC
+  start their answer with the `as-block` object of the AS's block. Its dates
+  were stored as the AS's (closes #168)
 - 2026-10-27: AS names keep their accented letters. The AS list built into
   RouteWatch is rebuilt from today's `as.csv`, which added a country code
   column. That file no longer lists AS 0 or the documentation AS numbers. A