Add the use case "application manipulating its own deployment"
This allows a YARN-aware app to talk to the AM to manipulate its deployment, without writing its own AM
That implies exposing more state for both viewing and manipulating. That includes state that is not retained over AM restart.
We may want to publish some event history purely for the apps too