Fix bad experience if you collect Allocation Stacks and the circular buffer wraps

[vancem]

The scenario is that you have a large allocation trace and it wraps in the circular buffer.

Today you lose the type events so you get many unknown types.

This happens both with the ClrProfiler collection as wellas the ETW based collection.

At least warn people about how to fix it.

[vancem]

We should look for a runtime startup event in the trace and if we don't find it for the process we should create a warning.

[github-actions]

Due to lack of recent activity, this issue has been labeled as 'stale'. It will be closed if no further activity occurs within 30 more days. Any new comment will remove the label.

[brianrob]

This is relevant for both the view that uses EtwClrProfiler events and for the one that uses the BulkType and GCSampledObjectAllocation events. For EtwClrProfiler, you need the ClassIDDefintion events. For GCSampledObjectAllocation events, you need the BulkType events.

Both of these require that the process be started after tracing starts, so we should look for the RuntimeStart event in the Microsoft-Windows-DotNETRuntime provider (not the rundown provider) and if we can't find it, when the user opens the view, pop-up a note that the trace may have overflowed the circular buffer and be missing type information. This can be fixed by re-capturing the trace with a shorter duration or a larger circular buffer.