[Feature Request]: Terminal Logger primary outputs should optionally use absolute paths

[baronfel]

Summary

In dotnet/sdk#38552 @tmds requested that the primary outputs of built projects be able to emit the absolute path instead of relative paths. While we don't think this should be the default behavior, some kind of knob here does make sense for their use case.

Background and Motivation

We chose relative paths for the output (with clickable/right-click-able directory urls) for readability and usability based on customer feedback from the first Terminal Logger releases. However some user workflows benefit from copying the direct file.

Proposed Feature

We should enable this either by emitting the absolute path visually, or by making the generated file://-scheme URIs (for terminals that support clickable links) emit absolute paths. This should be toggled via some option, it should not be the default.

Alternative Designs

No response

[baronfel]

This was also requested by @KalleOlaviNiemitalo in #9800 (comment).

We'll implement this by checking for the the GenerateFullPaths property, which other tools in the toolchain already set and make use of. TL breaks pretty badly when GenerateFullPaths is false - we need to figure out why that is.

We need to tackle two enablers first

• Make Terminal Logger respect verbosity #9810 - which separates the message pipeline verbosity from the rendering verbosity, giving us access to more messages in the implementation, and
• [Feature Request]: Convert Terminal Logger to a ForwardingLogger #9806 - which makes TL a forwarding logger, so that all of the nodes aren't sending every single evaluation message to the main node - only the ones that have useful data