eliminate single/multi writer distinction

eliminate single/multi writer distinction

After commit f4bdecc4ecce8bcbb2d8ccbb524ba1f3f76565ba, there is no
longer any distinction between SingleWriter and MultiWriter's handling
of read after write.

Databases that were SingleWriter still have lock files that are used to
prevent multiple writers.

This does make writing to such databases a bit more expensive,
because the MultiWriter code path that is now used opens a second db
connection in order to write to them.