Aletheia Integration - Long Term Branch

[TilakMaddy]

Perf gains !! 💪

• Support symlinks
• Soldeer support (right now, aderyn crashes when soldeer is found)
• Fixed version compilation
• EVM version detection
• Speed improvements? ..you bet.

Caveat:
While we manage to detect the EVM version and solc version, we don't do nothing with it yet. But this PR _gives the ability to do so, in the future

Misc:

No longer need to cargo publish these 2 crates -
cyfrin-foundry-compilers = "0.3.20-aderyn"
cyfrin-foundry-config = "0.2.1"

Aletheia is all in one.

One more cool benefit is that we only expose required stuff from aletheia so auto-complete feels better

TODO

• Find out why temple gold report is different and fix it.

  • I spent a whole day and not even close to knowing how why i get different ASTs (same number of nodes though) resulting in diff report. 😭 @alexroan can you help ?

  • I have verified

    • same compiler versions (current dev <> aletheia)
    • same set of files (current dev <> aletheia)
    • same error definitions ids (current dev <> aletheia)
    • DIFFERENT referenced_declaration (current dev <> aletheia) ...which causes false positives to show up

• Remove dev-dependencies on

  • cyfrin-foundry-compilers = "0.3.20-aderyn"
  • cyfrin-foundry-config = "0.2.1"

  (Basically have to re-write the testing arch using aletheia)

[TilakMaddy]

@alexroan Please 🙏 try this out locally on some of your repos and get back to me...

LMK if you notice a considerable performance gain

[TilakMaddy]

Probably our assumptions on how source maps work is incorrect.... :(

[TilakMaddy]

@alexroan Can you please run cargo build (so you build up cache) followed by cli/reportgen.sh in this branch. Then tell me if you are able to generate the same report for templegold as dev branch ?

Also you can try cargo prep --tg

that works too 😅 !!!