cf logs XXX --recent does not work when a deployment fails

[rmeharg]

Steps to reproduce:

• Deploy an application successfully
• Deploy the application again unsuccessfully, log message shows: TIP: use 'cf logs XXX-new-build-YYY --recent' for more information

Running cf logs XXX-new-build-YYY --recent or cf logs XXX --recent no longer works due to the way new deploys are created.

CF logs are lost when the new-build is deleted and the logs are only got from the Deployadactyl response.

This tip should be removed from the Deployadactyl output if the new-build is unsuccessful and deleted.

[trayo]

I'd like to remove it but that output comes from the Cloud Foundry CLI. In addition, those logs were also lost in the old way new builds were created.

We could probably implement some kind of parameter that doesn't trash the new build after deploying in order to leave it around for users to investigate.