MSBuild should preserve stacktraces when ToolTask exe throws an exception

From @jaredpar:

Why is it that MSBuild hides exception stack traces when a ToolTask exe throws an exception?
It takes easy to identify issues and turns them into bugs that can only be identified with a binary logger / verbose log

Classic example in this bug https://github.com/dotnet/roslyn/issues/25286

Here an experienced developer sees a compiler crash and has to throw their hands in the air because the error code is worthless. Yet binary log trivially shows the problem here.