Currently, the seeder will write its database files to the current
working directory. This is clumsy and can lead to starting the seeder
up without its database if it is started up from a different location.
This change will not only create a default directory for the seeder's
database files (and any future files it writes/reads) but also allow the
user to define where that data directory is.