Add fuzzing

[JarLob]

This PR adds fuzzing support for NanaZip specific formats as promised.
There is some overlap with #890 because the fuzzing is done with Asan instrumented build to catch memory access violations, but overall Asan build of NanaZip can be built on its own and used to run tests for example.

[JarLob]

The fuzzing / build-base is expected to fail in this PR since Asan build is still not in the main branch. Once accepted it will run fuzzing for 10 minutes for new PRs that make changes in relevant files.

[MouriNaruto]

Thanks. But I will make some changes and merge manually on the code side.

Also, for the test assets side, I need to know some opinions from @dinhngtu to know the assets store side.

But at least, I think we can say:

• ASAN mode PR and Fuzzing tests PR will be finally merged via multiple commits. (use co-authored-by to note you in all related commits)
• ASAN mode PR and Fuzzing tests PR will not be ported back to the 6.0 stable branch. But it should be OK because all source code changes in the NanaZip stable branch will be cherry-picked from the main branch, which smells like Linux kernel style.

Kenji Mouri

[JarLob]

Ok, let me know how it goes. I'm really curious because I basically vibe coded a replacement for https://google.github.io/clusterfuzzlite/ that runs on Windows.
Working in my repo, but if I notice any bugs I'll push new commits here.

[MouriNaruto]

@JarLob

According to #913, you will know:

• Some NanaZip-related work happens in the Mouri Internal Library Essentials (Project Mile), not only directly in the NanaZip repository.
• Recently, I have been working on essential utility functions in Mile.Mobility that can help make binary parsing safer.
  • So far, I have implemented Checked Arithmetic, Endian-independent Read and Write, and Sequence Compare in Mile.Mobility.Utilities.FixedInteger.
    • List: https://github.com/ProjectMile/Mile.Mobility/blob/main/Documents/Mile.Mobility.Utilities.FixedInteger.md
    • Header: https://github.com/ProjectMile/Mile.Mobility/blob/main/Mile.Mobility/Mile.Mobility.Utilities.FixedInteger.h
    • Source: https://github.com/ProjectMile/Mile.Mobility/blob/main/Mile.Mobility/Mile.Mobility.Utilities.FixedInteger.c
    • Test: https://github.com/ProjectMile/Mile.Mobility/blob/main/Mile.Mobility.Test/Mile.Mobility.Utilities.FixedInteger.Tests.cpp
  • I am also incubating and dogfooding memory-range-related utilities in the Mobility OS repository before they are formalized.
    • Header: https://github.com/MobilityOS/Mobility/blob/main/Mobility.Core/Mile.Mobility.Utilities.Memory.Unstaged.h
    • Source: https://github.com/MobilityOS/Mobility/blob/main/Mobility.Core/Mile.Mobility.Utilities.Memory.Unstaged.c

So, I also hope you can help me to review these headers/sources changes, which will be used in NanaZip, and it seems your PR will also have similar operation functions.

Kenji Mouri

[JarLob]

Will take a look when time permits.