Perl services can start up incompletely

[Galen Charlton]

If a Perl service's implementation module isn't successfully imported during startup (e.g., because of a missing dependency or a syntax error), the service can nonetheless get started and appear to run. However, in that state it will only offer the built-in methods such as opensrf.system.echo.

Rather than starting up an incomplete service, it would be better for all of the following to happen:

- the startup error get logged
- the service _not_ get started
- the problem get reported back to osrf_control