-fsanitize=fuzzer-no-link makes it workable to build a library with fuzzing
enabled, and let the fuzzing test program explicitly trigger the fuzzing.

This allows fuzzing to trace cmp instructions to guide the fuzzing to
improve results.

msan requires that we build all code with msan to avoid false positives.

This allows to cover
- another arch that x86, which is also very common
- an arch where char is unsigned
- a little-endian arch

This is running under qemu-user, so significantly slower and doesn't support
ptrace thus no address sanitizer etc. but at least the undefined sanitizer
works.

See: https://github.com/gradle/wrapper-validation-action

So developers get the 64bit results first

* Add: fuzzer files and modifications in config & compil
* add configure.ac change
* add minimize-corpus.sh
* add fuzzing directory and readme
* add to check if CC support libfuzzer
* Make workflow dump the crash POC
* Add debugging information
* Run fuzzing only once a week for now

Co-authored-by: kmamadoudram <[email protected]>
Co-authored-by: yocvito <[email protected]>
Co-authored-by: Samuel Thibault <[email protected]>

It seems that reprotest is breaking the gradle build

The tarball produced by make dist was missing a lot of files, so that
building from it would completely fail.

Now that all errors are fixed.

Otherwise they will go unnoticed.

Now that all memory errors are fixed.

Ref #220

Now that it is fixed by

dab5457620 "Fix deleting FrameManagerImpl*"
261954b4bd "Fix deleting SpeechWaveGenerator"

Now that all tsan errors are fixed.

Ref #220

Now that all lsan errors are fixed.

Ref #220

Now that all asan errors are fixed.

Ref #220

Now that all usan errors are fixed.

Ref #220