Make drupal console more graceful

[nvaken]

Currently, Drupal Console is really sensitive for Drupal errors. When we generate a cached error in Drupal rendering it unresponsive (500), you'd expect Drupal Console to be still responsive to be able help you rebuild the caches. The tool Drush seems to be able to handle these situations better and most of the time allows for a lot of the commands still being able to run. For completeness sake, I'm not only taling about cache rebuilding, but also other commands that would be usefull in a 500 situation (like outputting db logs).

As discussed with @jmolivas, we should be able to harden DC by making more use of try and catch statements.

I'll try to make some solid, reproducible situations soon and post them here.

[Jelle-S]

We had a similar issue with config that was messed up during one of our deploys (we're using DC to execute our db updates etc). There was a reference to a dependency (entity type or something similar, don't know exactly what it was anymore) that no longer existed. Because an exception was thrown during what I presume is DC bootstrap, none of the DC commands were loaded (no cache rebuild or db update commands). We removed the reference to the missing dependency in our codebase and did a new deploy. But because of this error in the config, DC could no longer bootstrap and, for example clear the cache and execute a db update. We had to switch these commands to the drush equivalents in our build script and deploy again to fix the error.

[enzolutions]

@nvaken I know this is an old issue, but could you confirm that still happening in 1.9.0 and is the error is still there, could you tell me how to reproduce.