[WFLY-4133] Hanging EJB threads because of a persistent timer and failed
deployment
TimerServiceImpl gets a new state (active). This avoids getting stuck
during failed deployments when the TimerService starts before the 
EJBComponent, causing an unrecoverable lock in
BasicComponent.waitForComponentStart
Merge pull request #7006 from elguardian/WFLY-4133

[WFLY-4133] Hanging EJB threads because of a persistent timer and failed deployment
Remove the use of newControllers in the EJB subsystem
WFLY-4125 Add option to disable EJB system exception logging