Add tests to verify that our init scripts conform to the LSB specification

Details

Description

I recently submitted BIGTOP-505 and BIGTOP-506, but we should proactively verify all our init scripts follow the LSB specification.
This would avoid some issues where for instance third party tools get confused by the return code of some action.

Here are some cased to be checked (extract from the spec linked above):

For all other init-script actions, the init script shall return an exit status of zero if the action was successful. Otherwise, the exit status shall be non-zero, as defined below. In addition to straightforward success, the following situations are also to be considered successful:
restarting a service (instead of reloading it) with the force-reload argument
running start on a service already running
running stop on a service already stopped or not running
running restart on a service already stopped or not running
running try-restart on a service already stopped or not running

Roman Shaposhnik
added a comment - 12/Apr/12 00:51 We do quite a bit of that here (more tests are welcome):
https://github.com/apache/bigtop/blob/trunk/bigtop-tests/test-artifacts/package/src/main/groovy/org/apache/bigtop/itest/packagesmoke/PackageTestCommon.groovy#L133
The trouble is that our automated package testing has fallen through the cracks.
We really should make it a priority for Bigtop 0.4.0 to at least run this stuff.