chore: evaluate instruction table initializer at compile time

[DaniPopes]

Currently the instruction table is always initialized at runtime on the stack, which bloats the stack of functions that create an EVM and is generally slower.

With this change the table gets compiled into a static and memcpy'd at runtime into the instruction table's Box.

[gakonst]

Nice -- this is the kind of change that I wonder why doesn't rust do by itself?

[codspeed-hq]

CodSpeed Performance Report

Merging #2762 will not alter performance

_{Comparing DaniPopes:const-instr-table (d41f582) with main (a5dd047)}

Summary

✅ 171 untouched benchmarks

[DaniPopes]

Because it does what you tell it to, generally it won't evaluate something at compile time just because it's const fn unless you force it through const X: ... or const {} because it technically has different semantics (initializing the array on the stack and moving elements into it, vs copying a constant)