Fix race condition where a transactional object is already locked but writeLocked has not been invoked yet. With multiple threads attempting to lockWrite at the same moment, the transactional object could reach an inconsistent state for a few nanoseconds.
ServiceController.shouldStart must always return false if service is disabled, regardless of mode
Remove allAreSet call from ServiceController.isMode(byte).

The method allAreSet cannot be used in this case to determine state because STATE_UP equals 0 and STATE_LAZY & STATE_ON_DEMAND could be equal either STATE_LAZY or STATE_ON_DEMAND.
Enable OneService_OneDep_TestCase