[FancyLogger] Show link to project outputs

[edvilme]

Fixes #

Context

One of the key features of the old console logger is showing the path to the output file for each project using the format
Project -> path/to/output.
To save space, FancyLogger only shows the filename of the output in a clickable link that redirects to the output file following the same format.

Changes Made

• Updated ANSIBuilder.Formatting.Hyperlink to support clickable hyperlinks
• Updated Regex for matching ANSI codes to also match hyperlinks
• TFMs now show in a white background

Testing

Notes

[rainersigwald]

This is really slick, but I think it hurts a critical use case: getting a path to an output so I can run it.

I often do

1. dotnet build
2. double-click output path message to get full path to a specific output
3. right click (copy)
4. right click (paste)
5. enter (run that thing)

I find this easier than dotnet run because you can build a whole solution and because you can iterate on adding args to the thing more quickly and easily.

Fortunately I think there's an easy fix: don't truncate the path, but still hyperlink it. Then I can copy/paste but also see it in Explorer.

[edvilme]

This is really slick, but I think it hurts a critical use case: getting a path to an output so I can run it.

I often do

1. dotnet build

2. double-click output path message to get full path to a specific output

3. right click (copy)

4. right click (paste)

5. enter (run that thing)

I find this easier than dotnet run because you can build a whole solution and because you can iterate on adding args to the thing more quickly and easily.

Fortunately I think there's an easy fix: don't truncate the path, but still hyperlink it. Then I can copy/paste but also see it in Explorer.

Alright. Do you think we should clip them if they're too long?

[rainersigwald]

Do you think we should clip them if they're too long?

I'm torn on this but lean toward "no, output the whole path". Would happily receive feedback!

[rainersigwald]

For follow-up PR: this should be a static Regex constructed with RegexOptions.Compiled, which should dramatically reduce overhead of scanning using it. On .NET 7, we should use a [GeneratedRegex].

[rainersigwald]

@edvilme can you please merge main after we land the 17.5 merge into main (I think doing those together will minimize merge conflicts).

[rainersigwald]

I merged #8314 into this speculatively and it's looking good but blocked on that, so drafted for now.

[rainersigwald]

Undrafted since #8314 went in. Still LGTM to me, so marking merge-when.