A 'start' operation only is available for a domain server resource when it is started

The server lifecycle ops are registered with the domain server resource by a call to ServerConfigResourceDefintion.registerServerLifecycleOperations. DomainModelControllerService registers that when the server registers with the HC.

This is odd in the case of 'start' as it means that op is only registered when the server is started.

Perhaps it should be registered with StoppedServerResource, although I haven't dug into what happens with that resource when the server is registered. If it is simply ignored that would be great.