Fuzzing the verifier using debugging builds is inefficient

The libfuzzer for the verifier is only acheiving around 3 iterations per second. With the size of the fuzzing space to be tested, this limits the amount of coverage we can acheive.

Proposal:
Create a FuzzerRelease configuration that builds with ASAN and full optimization. This will improve our overall fuzz coverage as it will complete more fuzzing during the scheduled CI/CD run.

Locate the verifier's libFuzzer build configuration and the scheduled CI/CD workflow, then compare the existing debugging build settings with the proposed FuzzerRelease configuration. Done means the fuzzing build uses ASAN with full optimization and achieves improved iteration throughput during the scheduled run.

Written by the indexing model from the issue text.