Make it possible to start and stop containers and executables that aren't weren't fully initialized by DCP

[davidfowl]

The 2 main scenarios are:

• Ability to stop and restart a resource in the waiting state (it may be waiting for a dependency to start
• Ability to start a resource that failed to start (e.g. a dependency load failure)

[JamesNK]

Ability to start a resource that failed to start (e.g. a dependency load failure)

What do you mean by this? I believe FailedToStart state resources can already be started.

The RuntimeUnhealthy can't be explicitly started from that state right now. Do you want it changed to allow the start command?

[JamesNK]

@karolz-ms Is there a situation where someone would want to be able to expliclty start a container via a resource command when the container is in a RuntimeUnhealthy state? I tested it out, and nothing happened, which is what I expected.

[davidfowl]

This is about refactoring the code in application executor so that commands can restart the entire workflow in the apphost and not just call dcp