Fix Blazor error logging to telemetry

[JamesNK]

Description

The error boundary in the dashboard prevents errors from being logged to the console and causes the page to go blank.

There is an error boundary in the dashboard to receive unhandled Blazor errors and send them to telemetry. This works. But the error boundary has negative side effects of blanking the page and preventing the error being logged to the app host console.

The impact on the user is they don't know why the page went blank. They don't get an error feedback in the browser or the console.

The fix is to remove the error boundary and use a logger provider instead. Blazor always writes an error message and we can use that as a hook to send the exception to telemetry.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[Copilot]

Pull Request Overview

This PR fixes the issue of Blazor error logging by replacing the TelemetryErrorBoundary with an ILoggerProvider that sends error details to telemetry, ensuring that errors are logged in the app host console.

• Introduces a new TelemetryLoggerProvider and associated TelemetryLogger class.
• Updates dependency injection in DashboardWebApplication to register the new logger provider.
• Removes the TelemetryErrorBoundary component.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/Aspire.Dashboard/Telemetry/TelemetryLoggerProvider.cs	Adds a new logger provider to capture and report telemetry for Blazor errors.
src/Aspire.Dashboard/DashboardWebApplication.cs	Registers the new TelemetryLoggerProvider in the DI container.
src/Aspire.Dashboard/Components/Controls/TelemetryErrorBoundary.cs	Removes the obsolete error boundary that was previously used for error logging.

[danmoseley]

compilation errors

[SteveSandersonMS]

I'm assuming this usage pattern adds a further ILoggerProvider rather than replacing the one that would already have been in place, so you still get normal logging output.

[JamesNK]

Yes. It's what happens when you call LoggerFactory.AddProvider: https://github.com/dotnet/runtime/blob/f76d75739482939fcf2661010bf490a3d81163ed/src/libraries/Microsoft.Extensions.Logging/src/LoggingBuilderExtensions.cs#L37

Other methods to add customer loggers use TryAddEnumerable. Example. I think that's to avoid double registration of a provider which isn't a problem in our case because we control all registrations in the dashboard app.

[JamesNK]

@SteveSandersonMS I added a test.

[danmoseley]

/backport to release/9.3

[github-actions]

Started backporting to release/9.3: https://github.com/dotnet/aspire/actions/runs/15023976015