Feat: integrate sierra-analyzer tool into forge

[Rog3rSm1th]

Introduced changes

This PR creates an analyzer subcommand in forge based on the sierra-analyzer tool from @FuzzingLabs. The available options allow you to decompile the Sierra once it's built, generate its control flow graph, its call graph and run security detectors on it.

$ ~ snforge analyze --help

Analyze the project using the sierra-analyzer

Usage: snforge analyze [OPTIONS] --contract <CONTRACT>

Options:
      --function <FUNCTION>
          Specify the function name to analyze
      --contract <CONTRACT>
          Specify the contract name to analyze
      --cfg
          Generate a CFG (Control Flow Graph) instead of normal output
      --callgraph
          Generate a Call Graph instead of normal output
  -v, --verbose
          Enable verbose decompiler output
  -d, --detectors
          Run the detectors
      --detector-names <DETECTOR_NAMES>
          List of detector names to run
  -h, --help
          Print help

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Performed self-review of the code
• Added changes to CHANGELOG.md

[cptartur]

Hey, this contribution is quite out of the blue. A couple of concerns:
First of all, what's the motivation for including this into Starknet Foundry? I see the linked tool is entirely standalone and I'm not sure what's the benefit in bundling it. Right now, we don't bundle anything intentionally - even "ours" profiler and coverage have to be installed separately.

Additionally, Starknet Foundry uses https://github.com/software-mansion/universal-sierra-compiler so we are pretty much independent from the Sierra version, is this true for the proposed changes?

Lastly, I see that a lot of code was basically copied over from the original repo, why isn't it used as a library? I'm agains introducing 124k lines of new code into foundry.