startup wizard launches even when `--help` and `--version` are supplied
~/.balsa exists, then running balsa always tries to initialize it.
I would expect that
balsa --help and
balsa --version (at least) would not bother trying to launch the setup wizard.
I believe this happens because the
startup signal fires first (
balsa_startup_cb, which invokes
config_init), then then
command-line signal (
GApplication docs seem to recommend handling things like
--version with the
handle-local-options signal instead of the standard command line handler.