I found a way to fix traces broken by the 100-stack-frame limit

## Background and Motivation

Hello,

As the title says, I found a way to recover traces that are affected by the 100-stack-frame limit. I pulled this off by carefully recovering the missing call stacks from a known good previous call stack sample. This logic is better explained in my blog post: https://dfamonteiro.com/posts/dotnet-trace-final-fix/.

And here's the fork with the changes detailed in my blog post: https://github.com/dfamonteiro/daniel-trace

I thought you might find this an interesting improvement opportunity to `dotnet-trace`

Start with the linked blog post and the fork containing the proposed changes for dotnet-trace. The issue names no repository files, tests, entry points, or acceptance criteria, so maintainers would need to identify the implementation area and define what a completed trace-recovery improvement should demonstrate.

Written by the indexing model from the issue text.