cargo build diagnostic improvements

[antonok-edm]

I use cargo objcopy to compile some projects, but the unformatted messages are challenging to scan visually. The diagnostics are also not printed if there is a build error.

For those two reasons, I often find myself falling back to cargo build instead. But that means sometimes I will only run cargo build, thus not creating a new version of the flashable binary, and losing track of whether or not my changes are doing anything.

Typing this out now, I realize that something like cargo build && cargo objcopy would probably solve most of my problems, but I think changing those two defaults would still be a big usability improvement over the current behavior of the binutils tools.

[antonok-edm]

CI failures are unrelated but I opened #155 to fix them as well.

that was merged 🎉