✨ feat: heimdallibrary (expose decompiler as library)

[perama-v]

What was wrong?

No access the decompiler within external rust code.

What was changed?

• Exposed the decompiler as a module (use heimdall::decompile;)
• Exposed CLI flags as methods in a builder pattern (DecompileBuilder::new(BYTECODE).decompile();)
  • This just wraps the existing DecompilerArgs inside the builder for a nice interface.
• Added an example to showcase use as library (cargo run --example decompile)
• Added simple test using the bytecode from test: benchmark_decompile_simple.
• Added basic docs for the builder
  • doctest set to no_run because the bytecode is truncated in the doc example: "7312/* snip */04ad"

Examples

Minimal use

use heimdall::decompile::DecompileBuilder;

const SOURCE: &'static str = "7312/* snip */04ad";

DecompileBuilder::new(SOURCE)
    .decompile();

Use of all builder (flag) methods:

use heimdall::decompile::DecompileBuilder;

const SOURCE: &'static str = "7312/* snip */04ad";

DecompileBuilder::new(SOURCE)
    .default(false)
    .include_sol(false)
    .output("my_contract_dir")
    .rpc("https://127.0.0.1:8545")
    .skip_resolving(true)
    .verbosity(5)
    .decompile();

Unchanged

The decode method was not exposed because, unlike the decompile method, no files are emitted.
It seemed less likely to be useful in the context of a library

Formatting

I did not run cargo fmt, as this produced changes across the codebase.

Linting

Clippy is happy, with some silencing with #[allow(dead_code)] on the builder pattern methods
(which are not technically called).

[perama-v]

I have also inadvertently included some whitespace trimming, my apologies

[Jon-Becker]

Looks good! I've added you to contributors, let me know if you need me to change any of the info there :)

I'll run some more tests later today and merge this ❤️ 🦦