Added support for custom resource logging

[davidfowl]

• Resources can call WithResourceLogger to add an annotation that allows them to publish logs to a live stream. These will flow through the resource server to any consumer (including the dashboard).
• Share circular buffer between otlp log storage and aspire.hosting.
• Added tests

Fixes #2498

custom-resource-logs.mp4

Microsoft Reviewers: Open in CodeFlow

[JamesNK]

I think console logs need the concept of paging. Returning all the data and displaying all the data is a performance problem, especially showing 1000s of lines in the browser.

Virtualization means only a subset of the data is needed.

I noticed this earlier when I created #2507

[mitchdenny]

Two thoughts on this:

1. Given we are constraining height of the logging pile (10000 entries). Should we also define a maximum width to the message so we know that on a per resource basis memory consumption cannot exceed X?
2. Should we also be looking to output these entries to the AppHost console log?

[mitchdenny]

Tentatively approving pending the fix on the test failure and responses to those questions above. They can be follow up PRs if needs be.

[davidfowl]

@mitchdenny

Given we are constraining height of the logging pile (10000 entries). Should we also define a maximum width to the message so we know that on a per resource basis memory consumption cannot exceed X?

I don't think so, at least not by default. We'll need something more durable eventually though. I'm not a fan of opening a temp file bug it might be required for longer log streams.

Should we also be looking to output these entries to the AppHost console log?

Nope, see #2396