add debug logging about bstore db schema upgrades

bstore was updated to v0.0.6 to add this logging.
this simplifies some of the db-handling code in mtastsdb,tlsrptdb,dmarcdb. we
now call the package-level Init() and Close() in all tests properly.

vendor/github.com/mjl-/bstore/doc.go

@@ -216,24 +216,24 @@ stays trivial (though not plan9, unfortunately). Although bstore is much more
 limited in so many aspects than sqlite, bstore also offers some advantages as
 well. Some points of comparison:
 
-- Cross-compilation and reproducibility: Trivial with bstore due to pure Go,
-  much harder with sqlite because of cgo.
-- Code complexity: low with bstore (7k lines including comments/docs), high
-  with sqlite.
-- Query language: mostly-type-checked function calls in bstore, free-form query
-  strings only checked at runtime with sqlite.
-- Functionality: very limited with bstore, much more full-featured with sqlite.
-- Schema management: mostly automatic based on Go type definitions in bstore,
-  manual with ALTER statements in sqlite.
-- Types and packing/parsing: automatic/transparent in bstore based on Go types
-  (including maps, slices, structs and custom MarshalBinary encoding), versus
-  manual scanning and parameter passing with sqlite with limited set of SQL
-  types.
-- Performance: low to good performance with bstore, high performance with
-  sqlite.
-- Database files: single file with bstore, several files with sqlite (due to
-  WAL or journal files).
-- Test coverage: decent coverage but limited real-world for bstore, versus
-  extremely thoroughly tested and with enormous real-world use.
+  - Cross-compilation and reproducibility: Trivial with bstore due to pure Go,
+    much harder with sqlite because of cgo.
+  - Code complexity: low with bstore (7k lines including comments/docs), high
+    with sqlite.
+  - Query language: mostly-type-checked function calls in bstore, free-form query
+    strings only checked at runtime with sqlite.
+  - Functionality: very limited with bstore, much more full-featured with sqlite.
+  - Schema management: mostly automatic based on Go type definitions in bstore,
+    manual with ALTER statements in sqlite.
+  - Types and packing/parsing: automatic/transparent in bstore based on Go types
+    (including maps, slices, structs and custom MarshalBinary encoding), versus
+    manual scanning and parameter passing with sqlite with limited set of SQL
+    types.
+  - Performance: low to good performance with bstore, high performance with
+    sqlite.
+  - Database files: single file with bstore, several files with sqlite (due to
+    WAL or journal files).
+  - Test coverage: decent coverage but limited real-world for bstore, versus
+    extremely thoroughly tested and with enormous real-world use.
 */
 package bstore