Speed up the vaultik and database package tests (closes #235)

In the Dockerfile test phase, internal/vaultik spent 23.6s of 31.9s in
36 tests run one at a time. 24 of them were serial only because they
call log.Initialize; they now call it before t.Parallel(), so the
logger is replaced before any parallel test runs. The 12 still serial
change the umask, TMPDIR, os.Stderr or time.Local.

TestLargeDatasets took 8.4s of the 9.8s internal/database run by
committing each of its 1,500 inserts on its own; it now makes them in
one transaction. TestDedupOnlySnapshotRestores gives its second backup
its own snapshot name instead of sleeping 1.1s for a new snapshot ID.

Model: opus-5-5

TODO.md

@@ -22,6 +22,16 @@ the tag exists and is exercised; what is left is merging `next` to
 
 # Completed Steps
 
+- 2026-10-07: Cut the time the `internal/vaultik` and `internal/database`
+  tests take ([issue #235](https://git.eeqj.de/sneak/vaultik/issues/235)).
+  Most of the `internal/vaultik` time went to 24 tests that ran one at a
+  time only because they call `log.Initialize`; they now call it before
+  `t.Parallel()`, as the package's other tests do. `TestLargeDatasets`
+  committed each of its 1,500 inserts on its own and now makes them in
+  one transaction. `TestDedupOnlySnapshotRestores` gives its second
+  backup its own snapshot name instead of sleeping past the one-second
+  timestamp in the snapshot ID.
+
 - 2026-10-07: Made two messages say only what is true
   ([issue #240](https://git.eeqj.de/sneak/vaultik/issues/240)). A config
   file that others can read was warned about as containing S3