[WFLY-1458] handle the managed container startup timeout properly

The managed container implementation assumes that the check if server
is running

  getManagementClient().isServerInRunningState()

is cheap, while in fact, it doesn't have to be. It's possible for this code
to end up waiting for response that won't come, and the IO will have
to time out. This timeout defaults to 5 seconds.

If this happens, then the container startup timeout, which defaults
to 1 minute, will actually be cca 50x bigger, which is certainly not desired.