define new "master database" workflow

The old LSB development workflow for database changes is no longer viable, as
only one person has access to the master database.

The different output formats of different versions of mysqldump, which is used
to dump a running database - which dump is subsequently committed to bzr so we
have a copy everyone can restore, causes unnecessary changes. If a dump is
done on a different version, it will look like every .sql file changed even if
the change was minor.

We've been applying patches on a master copy, dumping there, and committing -
that is, only one machine (mysqldump version) is ever used for generating the
updates to the bzr branch 'specdb'.

Since the LF master DB server can't support this workflow (no access for
developers to do this), we need another scheme, and this scheme must be in
place for restoring the full LSB development workflow.

One suggestion has been to use an LSB-specific copy of mysqldump, which if used
would allow dumps for commit to be made on any machines where that version
works.

Another thought is to just use one specific machine, but not the master, to do
this dump/restore.

There may be other options.

For any of these cases, we'll also need a piece of infrastructure which updates
the master DB, since the process will no longer update the master as a side
effect.