Feature request: Skip jump dest analysis

[nhtyy]

Skipping jumpdest analysis can save alot of work when running inside a zkVM.

This is because we can save on all the constraints needed to scan the bytecode and populate the jump table.

I would be happy to jam on this in the next couple weeks, I did a POC a while back, which just would panic on an invalid jump, but would be nice to see it upstreamed if supported.

[rakita]

Jumpdest analysis is done only once on contract creation, if you use bytecode from database it already contains jumptable.

In Evm framework (branch on main), unanalyzed bytecode is removed and the only option is to analyze it. On newest release you can check Bytecode::LegacyAnalyzed to skip jumpdest analysis