XamlCompiler.exe needs better logs

[azchohfi]

Describe the bug

Related to: #8871

There is no way to understand what is happening when XamlCompiler fails. It only returns -1, wven with diagnostic build on dotnet build.

Steps to reproduce the bug

I've tested this with 1.5 and 1.6 experimental 2, and the behavior is the same.
If the xaml compiler fails for whanever reason, there is no way to get the logs on a CI build.
-> buildTransitive\Microsoft.UI.Xaml.Markup.Compiler.interop.targets (590):

        <Exec Condition="'$(UseXamlCompilerExecutable)' == 'true'" Command='"$(XamlCompilerExePath)" "$(XamlCompilerExeInputJson)" "$(XamlCompilerExeOutputJson)"' />

There is absolutely nothing else being passed to the xaml compiler, no verbosity, so it doesn't log anything anywhere.

Expected behavior

Whenever there is a MSB3073 error, it should not simply say "xamlcompiler.exe exited with code 1."

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.6 Experimental 2: 1.6.240701003-experimental2

Windows version

Windows 11 (22H2): Build 22621

Additional context

No response