feat(cli): alternative compilation entrypoint

[Maddiaa0]

Overview

This PR adds a flag alternative-main -m --alt-main which allows the user to define an alternative macro as their runtime bytecode entry point.

Usage
Given a test huff file that looks like the following:

#define macro MAIN() {
    0x01
}

#define macro ALT_MAIN(){
    0x02
}

running huffc --bin-runtime -m ALT_MAIN will output 6002.

If a macro name is provided that does not exist it will panic with a macro not found error.

Rational

I am beginning to look at seriously implementing a huff lsp, from this i would like there to be a way to have tags on a macro / huff test definitions in the IDE that would allow directly triggering an interactive debugger (similar to how test appears over rust test blocks). Having this behaviour within the compiler will greatly reduce the amount of code that would be required to enable macro level debugging.
Ideal use-case would be something like this:

hevm/forge debug --code ${huffc <file>.huff --bin-runtime -m <MACRO_NAME>}

Where this would launch the user immediately into an interactive debugger.

Even better would be integrating this with a test.

#[test(calldata=<something>)]
macro HUFF_TEST = {
    ...
}

Where the test could be instantly compiled with the --calldata added as an arg to forge/hevm debug.

Requested feedback points

1. Do we want this feature?
2. As to how the current PR is implemented, please let me know if you would prefer an alternative approach to providing this functionality. I've had to change a whole lot of tests for the current usage. This feels slightly messy to me but I'm not sure if it is less messy than the alternatives.

[refcell]

LGTM 🚀 Killer job!

[refcell]

Similarly, opened up issue #222