feat: set backtrace frame context

[joshuap]

This uses the ProjectRoot option to set the context for the backtrace frames, which allows us to show just the application trace.

I put this together while testing the library, but my knowledge of .NET/C# is too limited to know if this will work reliably in production apps, and it needs tests. But it seems to work locally in the example app:

Sometimes we run into issues with compiled languages (I'm not sure what production stack frames look like), so this definitely needs some more manual testing to validate the approach.

Can you take a look when you get the chance, @subzero10?

Here's what we need if we move forward with this:

• Verify approach and that it's working
• Add tests
• Add documentation

[subzero10]

@joshuap can you please help me understand what you mean with the following:

which allows us to show just the application trace.

Maybe a screenshot of an error in HB "before" your changes and another "after" your changes?

[joshuap]

@joshuap can you please help me understand what you mean with the following:

which allows us to show just the application trace.

Maybe a screenshot of an error in HB "before" your changes and another "after" your changes?

Here's an example from Ruby. Notice that the application frames (which begin with the [PROJECT_ROOT] token) are displayed first, above the full backtrace (which includes both application and vendor frames):

HB supports two ways of specifying whether a frame/file belongs to an application vs. vendor code:

1. Substitute the absolute path to the configured project root with the [PROJECT_ROOT] token (the older method, which the Ruby gem and JS libraries use)
2. Add the context property (not to be confused with error context) for each backtrace line in the notice payload. Values for context are "app" or "all"

We should definitely add docs for this info to the client library spec.