Cross-targeting projects emit difficult to diagnose errors

### Steps to reproduce

Create a cross-targeting project that will emit an error on build. See
[xTargetError.zip](https://github.com/microsoft/msbuild/files/3163772/xTargetError.zip)

Build the project with various logger settings.

### Expected behavior
Some log setting that provides enough context to identify which configuration of the project is actually emitting the error

### Actual behavior
No logger setting provides sufficient data. You need to look at a binlog, or more closely inspect a detailed or normal level log to correlate error to other log statements which might include the TargetFramework value.

### Environment data
`msbuild /version` output:
Microsoft (R) Build Engine version 16.1.67-preview+g13843078ee for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

16.1.67.33811

OS info:

If applicable, version of the tool that invokes MSBuild (Visual Studio, dotnet CLI, etc):
dotnet

### Suggested solution

A potential solution for this would be to include global properties in the error spew where the project file is currently emitted.

For example, instead of
```
Class1.cs(6,8): error CS1029: #error: 'this is an error, but from which configuration?' [D:\scratch\xTargetError\xTargetError.csproj]
```
Emit
```
Class1.cs(6,8): error CS1029: #error: 'this is an error, but from which configuration?' [D:\scratch\xTargetError\xTargetError.csproj : TargetFramework=net46]
```

You could make this opt-in with a Console Logger Parameter.

/cc @stephentoub @nguerrera