The solution is based on clusterfuzzlite, libfuzzer, and oss-fuzz
technologies.
- Add the .clusterfuzzlite directory.
- Add the fuzz CI stage and fuzzing CI jobs.
- Add the fuzzing targets in the fuzz directory.
- Document fuzzing in doxygen.
Remove these as fuzz testing is not something that most people will do
and they are not used in ISC fuzz testing (a more extensive set of seeds
is used). In addition, it is easy enough to generate sample packets for
the fuzzer (something that is described in the developer documentation).
Indeed, with AFL, any file (not necessarily a DHCP packet) can be used
as a seed and useful results obtained.
1. Update to documentation concerning the running of until tests
which code is compiled with fuzzing enabled.
2. Correction of text of fuzzing-related initialization exception.
