Remove the per-peer route tables (closes #122)

The routing table in memory now holds every route, so the two per-peer route
tables go, with every write, delete, count and read that served them. The
prefix handler applies each update to the table, writes the table's changes
every second, and stores each new prefix with its first-seen time. The peer
delete, its retry on the next flush and the updates held for it go too. The
types and errors of the server's answers move to internal/server.

The image's memory settings fit a full table of about 1 GB: GOMEMLIMIT of
2.5 GiB, a 512 MiB page cache for the writing connection, and SQLite heap
limits of 768 MiB and 1 GiB. The README describes the new table, its
database copy and the memory budget.

Model: opus-5-5

Dockerfile

@@ -121,10 +121,11 @@ RUN chown -R routewatch:routewatch /app
 
 ENV XDG_DATA_HOME=/var/lib
 
-# Cap the Go heap at 1.5 GiB so the runtime collects harder before the
-# container's memory limit is reached. setpriv in the entrypoint preserves this
-# the way it does XDG_DATA_HOME above.
-ENV GOMEMLIMIT=1536MiB
+# Cap the Go heap at 2.5 GiB so the runtime collects harder before the
+# container's memory limit is reached. A full routing table takes about 1 GB
+# of it (README "Memory"). setpriv in the entrypoint preserves this the way it
+# does XDG_DATA_HOME above.
+ENV GOMEMLIMIT=2560MiB
 
 # Cap glibc's malloc arenas. The SQLite C library allocates and frees millions
 # of small page-cache chunks from many threads; glibc otherwise creates up to