Port Fuzz Test to CMake

[jouho]

Problem:

#4743 introduces an option to build/run fuzz test through CMake. There are multiple followup tasks that need to be done in order to fully port fuzz test from make to cmake. This issue is to track them:

• Use newer version of libfuzzer and automatically link against it with -fsanitize=fuzzer option: ci: use newer version of libFuzzer #4762
• Migrate CI fuzz to use cmake instead of make (GeneralFuzzBatch(done) + ScheduledFuzzBatch(done) + change omnibus to use new buildspec for fuzz(done))
• Follow cmake build idioms (w.r.t binary location & library location). This requires CI migration from make to cmake to be done first, as it may require some changes to runFuzzTest.sh that will break the build in make (WIP: ci: add more libcryptos for fuzz batch & follow cmake idioms #4795)
• Update usage guide for fuzz test in readme at https://github.com/aws/s2n-tls/tree/main/tests/fuzz#corpus (done in chore: remove make fuzz and AFL fuzz #4808)
• Remove make fuzz. CI migration needs to be done prior to this. At this point the porting is done (Also done in chore: remove make fuzz and AFL fuzz #4808)

Requirements / Acceptance Criteria:

Complete above tasks

Out of scope / Further improvements:

• Add ASAN and UBSAN option back after upgrading to newer libfuzzer. These were causing memory allocation issue in the CI. Potential clue: https://github.com/aws/s2n-tls/blob/main/utils/s2n_mem.c#L103-L112 (ci: Re-enable asan and ubsan for fuzz tests #4840 )
• Enable fuzz coverage as mentioned in ci: add buildspec file for scheduled fuzzing #4763. We will likely need to add compiler flags listed here
• Reduce total test runtime by running single-threaded fuzz test concurrently. Investigation is required to explain why this is safe to change. We need to investigate how much coverage we achieve with respect to runtime, possibly with a table graph. Coverage achievement difference between multi-threading and single-threading also needs to be investigated if we do decide to enable multi-threading
• Improve effectiveness of our fuzz tests (more info on this at https://quip-amazon.com/q9qEABhYNJ2Y/s2n-tls-Fuzzing-Effectiveness)