Service can attempt to start without config

[Cory Johns]

Based on https://bugs.launchpad.net/charm-gcp-integrator/+bug/1815034 and https://discourse.jujucharms.com/t/blocker-deploying-cdk-on-manual-deployment/582 it seems there are conditions which can allow some or all of the services to attempt to start without the relevant config files having been written. This can lead to misleading status messages and errors in the logs, hindering debugging. We need to detect if start_master has not been called, and avoid attempting to start the services as well as reporting it as such in the status.

[Cory Johns (johnsca)]

It looks like the issue might actually be on the worker instead of the master, but I think we should be doing similar checks & reporting on both.

[George Kraft (cynerva)]

I'm pretty sure we can't stop most of the systemd services from starting because snapd starts them as soon as you install the snap. Best we could do to reduce log spam there is to make the wrapper scripts not run the underlying service if the snap isn't configured yet.

No doubt the charms could be handling status better, though.

[Manfred Hampl (m-hampl)]

reverting spam changes to description and summary