Minidump demo breakpad

[thinkocapo]

Overview

The work in this PR reflects the curl + payload command used here https://docs.sentry.io/platforms/native/minidump/#minidump-additional for manually sending .dmp's to Sentry's API.

Questions

a few questions before merging, can look at them in person

What Native Crash Looks Like?

• the 'myotag' tag appeared under heatmap, but not under TAGS section
• 'release' appeared on rt-side sidebar and heatmap, but not under TAGS section <-- could be a general upload problem
• the 'histag' did same, but 'myotag' is still there?

What Capture Message Looks Like?

It is a .dmp sent with the Capture Message? Does Capture Message return an exit status to the C/C++ function?

• no tag and no release shown

This curl dmp is producing 1 or 2?

Looks like it's producing 2, interesting.

We did for 'release' and 'tags' - try for other things?

• breadcrumbs (a lot of work, formatting-wise), etc.
• are release+tags sufficient for the time being? that's what our documentation covers

Note

• mention that you can do it with your own .dmp? any .dmp will work?

[ndmanvar]

@thinkocapo as discussed, lets move the curl stuff to the makefile
so all you have to do is make curl_minidump

[thinkocapo]

added make curl_minidump to Make file and it uploads a Native Crash but not a Sentry Message Capture. also, having the inconsistency problem where the native crash is not symbolicated, even with normal running of sentry-native make run command.

Not sure why make run sends 2 Events (using that one .dmp file in ./sentry-db/completed) but make curl_minidump uses the same .dmp and only sends Native Crashes (and it's sending 2, not 1, which is very confusing).

make run ends up calling...bin/example <--so this must play a responsibility in getting Sentry Capture Message to work. need to dig into that somehow.