Notify MSBuild TerminalLogger of project cache plugin run

[mruxmohan4]

Context

With MSBuild terminal logger (TL) enabled, project cache plugin (PCP) command-line output suppresses important information, which indicates whether projects have finished upon cache hits.

With both TL and PCP enabled (for "Cache Hit" scenario):

MSBuild version 17.11.0-dev-24217-01+5d2331ee1 for .NET Framework
Restore complete (8.4s)

Build succeeded in 38.4s

Changes Made

Adds information per-project to determine whether the project is classified as a cache plugin project, which occurs when the cache plugin target is called (prior to GetTargetPath or Build). For cache plugin projects that are built, the scenario remains the same (the output path is shown). For cache plugin projects that result in a hit, indicate the output path as well to indicate build progression.

Testing

This was tested with a custom package on the project cache plugin side to invoke the custom target and custom MSBuild bits, with TL and PCP enabled.
"Cache Hit" output:

MSBuild version 17.11.0-dev-24222-01+69635ee15 for .NET Framework
Restore complete (5.0s)
  CloudBuild.Core succeeded (0.4s) → c:\src\CloudBuild\private\Common\CloudBuild.Core\src\bin\x64\Debug\CloudBuild.Core.dll
  CloudBuild.Common succeeded (0.0s) → c:\src\CloudBuild\private\Common\CloudBuild.Common\src\bin\x64\Debug\CloudBuild.Common.dll
  QuickBuild.Hosting succeeded (0.0s) → bin\x64\Debug\QuickBuild.Hosting.dll

Build succeeded in 24.3s

"Cache Hit" (binlog):

"Cache Miss" output (same as before change):

MSBuild version 17.11.0-dev-24222-01+69635ee15 for .NET Framework
Restore complete (2.8s)
  CloudBuild.Core succeeded (0.0s) → c:\src\CloudBuild\private\Common\CloudBuild.Core\src\bin\x64\Debug\CloudBuild.Core.dll
  CloudBuild.Common succeeded (0.0s) → c:\src\CloudBuild\private\Common\CloudBuild.Common\src\bin\x64\Debug\CloudBuild.Common.dll
  QuickBuild.Hosting succeeded (19.0s) → bin\x64\Debug\QuickBuild.Hosting.dll

Build succeeded in 40.0s

"Cache Miss" (binlog):

Notes

N/A

[AR-May]

LGTM

[rainersigwald]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).