Allow --irOptimized output selection in ethdebug.

[aarlt]

• I removed the messages within the soltest tests - having messages there is super annoying in case of changes
• added more command-line tests
• the old version only allowed --ir in output selection, that created some confusion because --ir-optimized is always used within the via-ir pipeline, even if optimization is disabled. it will just set minimal optimzation, where the result will be always based on optimized yul - thats why --ir-optimized need to be allowed.

[clonker]

Mostly style stuff, nothing really wrong with it. Some stuff, especially in the boost testing department could/should be improved but that could also be done in a follow-up post-release - in my opinion at least :).
Perhaps we should (in a follow-up) also think about how to test these flag combinations better. I find it quite hard to parse, what combinations are actually tested and what the expected outcome is. Maybe this could be done in eg a shell script test (with these ~ prefixes) where you have one test for unsupported flag combinations / json inputs which then just asserts that we error out and perhaps check the error message and one test with supported combinations where you just grep if some expected key string is contained in the output. Something like that. Then at least to me it would be clearer what the test coverage actually is and all the relevant stuff is next to each other. Food for thought :)

[clonker]

Same as with the other test, I think this would benefit greatly from using data test cases and consequently unrolling the loops

[cameel]

Come on, pass it through jq at least :) 1-space indents are just WTF.

[aarlt]

I totally agree here - not sure what happened 😅

[clonker]

Just two more little formatting things I found. For the input json files there's also a bit of a mix going on with two-space indents and tab indentations - I am not sure which one is the preferred one :)

[cameel]

For the input json files there's also a bit of a mix going on with two-space indents and tab indentations - I am not sure which one is the preferred one :)

There is no situation where we use 1 or 2 space indents other than by mistake. It's always either 4 spaces or a tab in our codebase.