Profiling - `unknown` stacks on net8

[vaind]

On the current main branch, our Sentry.Samples.Console.Profiling gets captured with partially missing stack trace information.

I've debugged EventPipe capture & TraceLog and bisected historical releases and it turns out this is caused by an upgrade to net8.
When I try the sample on v4.13.0 branch it works fine. After changing the target framework in the sample to net8, it breaks and we get these missing stack traces.
Additionally, I've found out that increasing the CircularBufferMB in StartEventPipeSession to a higher value helps with the issue on the 4.13 branch, indicating it's caused by the initial rundown being too large so some information is dropped. However, the same "fix" doesn't work on 5.0 or main so I'm continuing investigation.

[vaind]

Looks like something changed in net8 that broke our usage of EventPipe. Raised an issue here: microsoft/perfview#2155 to try and figure out how to resolve this.