[desktop] Default build output on Windows too terse for non-Dart failures

[duncanmak]

I had trouble debugging a Windows build failure because the default output from flutter run is too terse.

❯ flutter run -d windows
Launching lib\main.dart on Windows in debug mode...
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(238,5): 
error MSB8066: Custom build for 'C:\Users\duncan\git\noticias\build\windows\CMakeFiles\776e9719f5f8ecedc9c205c7760b5085\flutter_windows.dll.rule;C:\Users\duncan\git\noticias\build\windows\CMakeFiles\80ea5e8e230c9e6159bcd1e86c54b144\flutter_assemble.rule' 
exited with code 1. [C:\Users\duncan\git\noticias\build\windows\flutter\flutter_assemble.vcxproj]
Building Windows application...
Exception: Build process failed.

Running flutter run -v gave me much better logs:

[  +11 ms]   [  +10 ms] Target debug_bundle_windows_assets failed: FileSystemException: Exists failed, path =
'C:\Users\duncan\git\noticias\assets\lib\ps\' (OS Error: The filename, directory name, or volume label syntax is
incorrect.

The default output can be tweaked to include better diagnostic information.

[stuartmorgan]

Looks like maybe we want "target .* failed:" in the error extraction regex.

[flutter-triage-bot[bot]]

The triaged-desktop label is irrelevant if there is no team-desktop label or fyi-desktop label.