Report crashes from tasks in minidump form #2313
Description
One thing that has come up from our use of OneFuzz is that our fuzzers may occasionally crash in production from unintentional bugs.
Because we're adding more complexity to our fuzzers and allowing third parties to write their own fuzzers, it's becoming more important that we're able to properly report errors in the fuzzers themselves as they are discovered in production so that we can either triage and fix the bugs ourselves or forward the relevant information to the third-party fuzzer developers so that they can fix the bugs.
However, while debugging panics printed to stdout is effective when that occurs from Rust or Go panics, we may still be faced with traditional access violations and other bugs from our particular setup that do not print any output.
In that case, it'd be best if crashes could be intercepted and dumped into minidump form, using the rust-minidump library suite. They can then be logged to some other service like Sentry that can be set up to notify us via Teams.