Starting integration tests

[tevoinea]

Summary of the Pull Request

Closes #3422

Adds an integration test for the local template fuzzing feature.

Info on Pull Request

What does this include?

• Updates to CI
  • Build simple-libfuzzer
  • Place the binary into the integration test directory
  • Run integration tests in CI
• Bump pete to version 0.12, this fixes a bug on linux where it was calling waitpid on all subprocesses instead of just the ones we're trying to debug
• Expose a onefuzz_task_lib crate, allowing us to write integration tests using rust's testing framework
• An integration test for a basic libfuzzer template including fuzzing, coverage, and crash reporting
• Fix a bug in path preparation on Windows when absolute paths are given

Validation Steps Performed

How does someone test & validate?

[codecov-commenter]

Codecov Report

Merging #3438 (9e9c548) into main (6e2cb14) will increase coverage by 4.38%. The diff coverage is 88.23%.

@@            Coverage Diff             @@
##             main    #3438      +/-   ##
==========================================
+ Coverage   34.42%   38.80%   +4.38%     
==========================================
  Files         299      271      -28     
  Lines       36259    31282    -4977     
==========================================
- Hits        12481    12139     -342     
+ Misses      23778    19143    -4635     

Files Changed	Coverage Δ
...c/agent/onefuzz-task/src/tasks/coverage/generic.rs	81.61% <66.66%> (+81.61%)	:arrow_up:
src/agent/onefuzz/src/libfuzzer.rs	78.62% <83.33%> (+11.21%)	:arrow_up:
src/agent/coverage/src/record/linux/debugger.rs	93.08% <100.00%> (+25.32%)	:arrow_up:
...nt/onefuzz-task/src/tasks/fuzz/libfuzzer/common.rs	84.22% <100.00%> (+67.91%)	:arrow_up:

... and 83 files with indirect coverage changes