chore(evm): remove trace printer, trim inspector stack

[DaniPopes]

I don't think this has much use, and is only exposed in cast run.
Additionally, trim inspector stack implementation when the internal inspector does nothing

[onbjerg]

i agree w this but would want another review because i lost original context on why this was even added

[klkvr]

lgtm, --trace-printer output is barely readable, we have cast run --debug so it should be fine

[drortirosh]

Why was it removed?

It provides a low-level tracing information even on blockchains that doesn't support debug_trace APIs, which is great.

An example of an issue I currently try to handle (and had to recompile an old cast for it)
We try to assess the cost of "post-verkle" of contracts.
To do so, we need a trace of all opcodes executed (e.g. a sequence of [address,PC])
We then calculate the code "slots" accessed.
But as I said, this can't be done without this tracing capability.