MaxScale tries to start up if --export-config is used and a cached cluster configuration is present

If configuration synchronization is enabled and --export-config is used when a cached cluster configuration is present, MaxScale will attempt to start up normally instead of exiting once the configuration is verified and exported. If another MaxScale is already running, this will cause the export to fail.

Another problem is that if the startup is fixed to not proceed past the verification phase, the configuration export will not produce any output as the static files it uses to produce the data will be empty.