regression task suggestions

[bmc-msft]

As is, the regression task implements something primarily useful to answer "does this build have this bug". However, this makes service-level integration of "tell me what bugs I've fixed" difficult.

This PR changes the flow slightly always creating a RegressionReport regardless of outcome. On repeating the crash, this report will include crash_test_result.crash_result. On not repeating the crash, this report will include crash_test_result.no_repro.

This probably impacts the git bisect workflow, but enables the tell me if we fixed a bug workflow in addition to tell me if we still have a bug workflow.

To demonstrate this idea, I added libfuzzer-regression test binaries of broken.exe and fixed.exe (not yet included in integration testing). As you would expect by the name, broken.exe has a bug and fixed.exe does not.

We can demonstrate this by doing the following:

PROJ=regress
NAME=regress
onefuzz template libfuzzer basic --vm_count 1 --duration 1 --target_exe ./broken.exe $PROJ $NAME 1 linux --wait_for_files unique_reports
onefuzz template stop ${PROJ} ${NAME}
onefuzz template libfuzzer basic --vm_count 1 --duration 1 --target_exe ./fixed.exe $PROJ $NAME 2 linux --wait_for_files regression_reports 
onefuzz template stop ${PROJ} ${NAME}
onefuzz template libfuzzer basic --vm_count 1 --duration 1 --target_exe ./broken.exe $PROJ $NAME 3 linux --wait_for_files regression_reports

During the first job, we'll see a single unique crash report created and no regression reports.

During the second job, we'll still have that unique one crash report. In the job specific regression reports container, now we'll have a regression report. Upon pulling that regression report, we'll see that the crash_test_result.no_repro exists.

During the third job, we'll still have that unique one crash report. In the job specific regression reports container, now we'll have a regression report. Upon pulling that regression report, we'll see that the crash_test_result.crash_result exists.