Log failure to run CLI command
Prior code only conditionally logged the output when `LOTUS_DEV` env
var was present. This doesn't make sense for a number of reasons:
* In case of an error starting up `lotus daemon` via systemctl for
example the logs would miss the error. One then has to search through
system journal to see what happened.
* There are no other places that I can find where `LOTUS_DEV` env var is
used. The commit that introduced this condition is very old with no
clear commit message to shed light into the rationale.
For the first reason alone, the changes here remove that condition, and
log the message when the logging output is not standard err or out. This
way we at least cover the case where lotus is run in a production
environment and would avoid partial logging of errors.
We were ignoring quite a few error cases, and had one case where we weren't
actually updating state where we wanted to. Unfortunately, if the linter doesn't
pass, nobody has any reason to actually check lint failures in CI.
There are three remaining XXXs marked in the code for lint.
