Crash reporting use cases

Crash reports and telemetry helps us greatly in finding any issues in Batch Explorer. Here are a few examples of issues that were fixed by automated crash reporting.

In general any issues marked with the from telemetry label are coming from telemetry.

Release 0.18.1 - issue with pool configuration #1638

A null pointer exception caused the pool configuration page to crash and show a blank screen. This error was detected very soon by the telemetry which allowed to push a hot-fix as version 0.18.1 to resolve this issue.

Release 0.19.1 - issue with job schedule create experience #1844

Issue due to a refactor broke the job schedule experience. Crash reporting allow us to detect and resolve this major issue in a short time. This was also bundled with 2 other smaller issues found with crash reporting