`Cardinal` and decoupling `RunTimeSeal`

[StandingPadAnimations]

The idea is to decouple RunTimeSeal from the interpreter and replace it with Cardinal. Cardinal wraps around the interpreter process and acts like a simple kernel, handling extension calls and all that

Pros:

• Easier to secure
• Simpler to understand then RunTimeSeal
• Implementing things like permissions is a piece of cake and doesn't require much refactoring of the interpreter Cons:
• Massive refactoring needed
• Removal of some bytecode instructions
• ExtCall needs to be replaced with some sort of system instruction

[dynafide]

I think this design is too complicated for this project. This design would be useful if Resurgence were a standalone VM application similar to the Java JVM, but for our goal of ease of embedding, I think the current design is better because it is easier for the user to manage, doesn't have any unneeded complexity, and the runtime comes fully isolated out of the box.