VM/EVM: More Code-Separation for Verkle Logic

[holgerd77]

Verkle logic is now very broadly integrated into VM/EVM with a lot of in-code 6800-switches and then doing Verkle logic, in EVM in particular all the accessWitness tracking.

Do not have the full picture yet and also not yet a working/practical structural approach, but it would be nice if we would better separate here, for some general better code structuring (this is getting some spaghetti-code tendencies) as well as (optimally) for tree shaking, both within the EVM (so that the EVM(VM) verkle code just is not getting in for non-Verkle usages.

But also - likely bigger - also for the state manager scope with the VerkleStateManager and AccessWitness now always getting in also for all non-Verkle usages.

Open for some rounds of discussion and brainstorming. This also likely need deep looks into the code and some solid thinking about structures.

[holgerd77]

Will close here, no follow-up respectively additional ideas represented, also still not fully sure if practical. Would nevertheless be pretty valuable if someone side-stumble upon ideas on this!