[nasa/cryptolib#369] Fuzz Testing in Docker

[jlucas9]

Moved the fuzzing harness provided by @mirkobitetto into the support directory and added a check for VirtualBox shared folders as the hard links required won't function with it.

How to test?

• Confirm you're in a repository cloned locally in Linux and NOT using shared folders
• git checkout cryptolib#369-fuzz
• cd support
• docker build -t ivvitc/cryptolib:dev .
• cd ..
• make clean
• make debug
• cd support/fuzz/scripts
• ./build-fuzz.sh
• cd ..
• python3 generate_corpus.py
• cd scripts
• ./run-fuzz-multithreaded.sh
• Manually confirm that fuzzer executing

Prior to closing merge:

• Generate new docker container for use
• Update workflow to use new container
• Update env.sh to use new container

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.71%. Comparing base (d72b9e2) to head (d2a730b).

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #456      +/-   ##
==========================================
+ Coverage   74.99%   82.71%   +7.71%     
==========================================
  Files          80       39      -41     
  Lines       23341    11762   -11579     
  Branches     1872      942     -930     
==========================================
- Hits        17505     9729    -7776     
+ Misses       5168     1675    -3493     
+ Partials      668      358     -310     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Donnie-Ice]

Working on my end! I'd like to try to work with the fuzz harness a bit to be more efficient, but that can be another issue.