Because MoneyGo requires sending passwords and session cookies, we
should never serve over HTTP. While we're at it, make it more convenient
for folks to test this out by adding a config option to auto-generate
self-signed certificates.
This is done by requiring 'parseTime=true' in the MySQL DSN's (required
by github.com/go-sql-driver/mysql when Scan()ing to time.Time's), and
not forcing update counts to match if rows were updated to what they
already were.
It was being used for session management, but we weren't using any of
the features that differentiated it from using go's cookies directly so
it is hard to justify the additional dependencies.
Still needs some fixups:
* UI is incomplete
* Investment transactions are unbalanced initially
* OFX imports don't detect if one of the description fields for a
transaction is empty (to fall back on another)
* I'm sure plenty of other issues I haven't discovered yet
