initial work on adding fuzzing to kerngen Parser

[michaelbeale-IL]

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers
why we should accept this pull request. If it fixes a bug or resolves a feature
request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce to the HE Toolkit project?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you are unsure about any of them, do not hesitate to ask. We are
here to help! This is simply a reminder of what we are going to look for before
merging your code.

• I have read the CONTRIBUTING agreement
• Current formatting and unit tests / base functionality passes locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

Setup

1. update virtual environment with updated requirements.txt file (two new dependencies, atheris and coverage)
2. cd to kerngen/fuzzing

How to run

Basic Fuzzing command: python3 -m high_parser_fuzzer CORPUS
Fuzzing with code coverage: python3 -m coverage run high_parser_fuzzer.py -atheris_runs=50000 CORPUS

NOTE: -atheris_rus= controls how long the fuzzer runs. The longer it runs, the more likely it is to find something.

How to generate coverage report

python3 -m coverage coverage-report
cd coverage-report && python3 -m http.server 8000

[michaelbeale-IL]

Closing PR until Dependabot problem is fixed.