Support for .NET minidumps on CoreCLR JIT

### Problem Statement

An experiment was made to [use `sentry-native` and capture minidumps (through crashpad)](https://github.com/getsentry/sentry-dotnet-minidump).

In the process we found out that the minidump created by crashed doesn't include information about the .NET runtime required on the backend to show things like managed heap, etc.

For that reason, the minidump support at this time is suboptimal, for example, not showing managed code lines in stack traces.

Tracking AOT support here: https://github.com/getsentry/sentry-dotnet/issues/2770

### Solution Brainstorm

A [discussion was opened on that repo with alternative methods to collect the minidumps, using .NET APIs or out of process collection.](https://github.com/getsentry/sentry-dotnet-minidump/issues/1#issue-782438188)

In addition, Sentry (backend/frontend) would require changes to read on the new sections in the minidump and display them to the users. Similar to how other .NET debugging tools do.

See also:
* https://github.com/getsentry/symbolicator/issues/1731