Process reconfigure failures and print out a message
From #2533 (closed)
Since #2533 (closed) got implemented, we have a way of specifying deprecation messages at the end of reconfigure.
Next iteration of this is to see how we can catch errors during reconfigure and present them to users.
For example: We periodically get db:migrate
failures that print a huge stack trace which completely confuses users.
Ideally, we would want to just take the actual migration failure and repeat it at the end of the reconfigure run.
We can then look into expanding with more standard failures such as, syntax errors, service not running, and similar.