Support for Cross-Manifold Abstraction

We briefly talked about this on the Ethereum Day in Berlin.
I wanted to document it here to not create a knowledge pocket within the org.
Since the Philosophy of this project is basically: Don't enable the contract devs to shoot themselves in the foot.
We also should think about a Cross-Manifold abstraction. A user shouldn't have to think about the edges of the Manifold.
Of course, this requires a whole [new paradigm of thinking](https://github.com/Citrullin/Sovereignty-Stack/blob/main/QUANTUM_SOCIAL_PHYSICS.md). (Maybe Actor-System for Contracts?)
Already described it in a higher level what this could mean for the [New Ethereum vision](https://medium.com/@citrullin/a-vision-for-new-ethereum-quantum-social-physics-the-end-of-the-one-world-computer-8a8000459e64) here.
Just went to an event yesterday where the BIS talked about [project Agora](https://www.bis.org/about/bisih/topics/fmis/agora.htm). We are clearly moving in this direction.
Since it's also EVM, it probably makes sense to target ONLY EVM at the beginning.
Long term SVM, WebAssembly etc. HAVE TO be included as well. NeoEVM might straight up work too as target.
From a design perspective, you should probably already take that into considerations, even when not implemented yet.
From a business perspective, you can also apply to multiple technology funds, giving you a more diverse revenue stream.
Plus a derisking from one specific technology. There are also still Evmos for Comsos, IOTA, Hedera etc.
The infrastructure for this is mostly already here, we mostly only have to change the way we operate.

Looking forward for your input on this one. Have a great day.
Ahh, the fuzz testing for the compiler can be improved this way too.
With the whole Gherkin Intents. Well, check it out :D

Start by reading QUANTUM_SOCIAL_PHYSICS.md and the linked New Ethereum vision to understand the proposed abstraction; the issue names no implementation files or tests. Review the compiler fuzz-testing and Gherkin Intents references, then seek an agreed EVM-first design and clear scope before implementation, with future SVM and WebAssembly targets accounted for.

Written by the indexing model from the issue text.