LifecycleAware components do not receive 'start' signal until first restart after setup

The signal is triggered after the database has been setup and the plugin system is started for the first place, but it is muted in DefaultLifecycleManager because at that point the setup process is not complete.

When the setup process is complete and the application is ready to receive requests, no signal is given to the LifecycleAware components.

This causes problems for some plugins, like Atlassian Healthcheck, which reports "unhealthy" due to https://ecosystem.atlassian.net/browse/AHC-47