JBIDE-18094

It would possibly make sense as a parameter to setServerStarting, for OUR servertypes.  There's no guarantee that this would make sense for other server types, at least no more than other possible flags would.  Unfortunately, this is API and would require changes to many places, as well as fuse. I don't think it'd affect openshift. 

Personally, I think it fits best in the individual launch configurations of a server, rather than in the as.wtp.core's Controllable Server Behavior infrastructure.   I'm hesitant to move it to a utility method, because as far as I can tell, that utility method would basically just be a method with 2 lines in it, and I don't think it justifies it. Also I'd need to find a proper place for that utility method, and I don't see any logical places such a method would belong. 

The class heirarchy of our launch participants makes it so that it wouldn't fit in a superclass (the rse launches have a different heirarchy) unless I put it in 2 separate superclasses. If it was in a standalone launch utility class, It'd be a new class with 1 method with 2 lines. Seems very... unproductive really.