perf(vm): hoist allowDynamicEnergy out of the opcode loop

[yanghang8612]

Summary

Follow-up to #6857. That PR routed every VMConfig getter through a thread-local current() (process-global snapshot + per-constant-call override). VM.play reads VMConfig.allowDynamicEnergy() once per executed opcode, so after #6857 each opcode now pays a ThreadLocal.get() on the block-processing hot path, where before it was a plain, inlinable static read.

CPU profiling (release_v4.8.2 vs master, same workload) shows new hot frames on 4.8.2 that are absent on master:

• org.tron.core.vm.config.VMConfig.current
• java.lang.ThreadLocal$ThreadLocalMap.getEntryAfterMiss — the localSnapshot lookup falls onto the linear-probe miss path on the block thread, which never installs a thread-local view.

The flag is VM config: it is loaded once in VMActuator.validate and is immutable for the whole execution. Reading it once per execution instead of once per opcode is therefore semantically identical and restores the pre-#6857 hot-path cost.

vmTrace() is intentionally left untouched — it was not migrated to the snapshot in #6857 and is still a plain static read.

Test

• :actuator:compileJava green.
• org.tron.common.runtime.vm.OperationsTest green (exercises the VM.play loop including dynamic-energy / suicide / vote-witness paths).