[.NET10] Epic: Investigate paths to help users be more successful discovering memory and layout issues

### Description

We are in the process of investigating various paths to help users better locate memory issues and narrow down performance bottlenecks.

We will update this issue with sub items as the discussion continues.

### Areas to Investigate

- OpenTelemetry
- Can we expose information about leaking types and performance issues through Telemetry? [Nalu Framework](https://github.com/nalu-development/nalu/blob/9b026eea531fc858ca2cff62524511f0a874be5d/Source/Nalu.Maui.Navigation/Internals/LeakDetector.cs#L5) has a really good example how to add some leak tracking to keep track if your pages are leaking
- Make it easier for users to generate dump files and speedscopes

Start by reviewing the listed OpenTelemetry investigation and the linked Nalu Framework LeakDetector example, then examine the proposed path for generating dump files and speedscopes. The issue is an open-ended epic; done would require a concrete, agreed investigation outcome or scoped sub-issue, which the current text does not define.

Written by the indexing model from the issue text.