[FUZZER] Multiple utils and library refactor, fuzzers

[zi0Black]

Description

New structure for utils:

./utils
├── authenticator.rs
├── helpers.rs 
├── mod.rs
└── vm.rs

helpers.rs contains generic data structures and helpful functions. Specific data structures or functions for specific fuzzers are now located in vm.rs and authenticator.rs.

testsuite/fuzz/src/main.rs is now a CLI that introduces helpful commands to build fuzzers. Currently, only compile_federated_jwk has been introduced, but others can be ported. This is a good PoC to show how to generate custom scripts/modules and embed them in the fuzzer's code if required for the setup. A new data folder is now present, which is used for support files for the new CLI.

I turned all the fuzzers back on, as the build now works as expected on OSS-Fuzz.

How Has This Been Tested?

./fuzz.sh test

Key Areas to Review

N/A

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 39m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
rust-move-tests	9m	🟩
rust-move-tests	9m	🟩
rust-move-tests	9m	⬜
rust-cargo-deny	5m	🟩 🟩 🟩
check-dynamic-deps	3m	🟩 🟩 🟩
general-lints	1m	🟩 🟩 🟩
semgrep/ci	1m	🟩 🟩 🟩
file_change_determinator	36s	🟩 🟩 🟩
permission-check	11s	🟩 🟩 🟩
permission-check	8s	🟩 🟩 🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[gedigi]

will this replace fuzz.sh?

[zi0Black]

We can; I haven't decided about it yet. So far, it’s helpful for accessing data structures and functionalities of other suites in Rust. Thought, most of the utilities would basically call other binaries.

[gedigi]

it may be confusing having two different utilities for the same purpose. can the functionality here be included in fuzz.sh ?

[zi0Black]

I can call It from the script, but it seems a bit layered, let me think about it.