feat: add runtime

[bidhan-a]

Summary

Add a lightweight runtime that encapsulates the VM and provides a higher-level execution layer for sBPF programs. It includes a simple account store, manages multiple VMs for CPIs, and provides syscalls implementation. Instead of interacting directly with the low-level VM, the runtime can be used to load and execute sBPF programs.

Updates

1. Added runtime crate
2. Moved some reusable logic (including syscalls implementation) from debugger to runtime
3. Updated debugger to use the runtime instead of vm

[alnoki]

@bidhan-a will this interact with Mollusk at all?

[bidhan-a]

@bidhan-a will this interact with Mollusk at all?

Not necessarily. But it can be used to build a test harness like Mollusk. For example - here's a test that checks the same program using both Mollusk and the runtime.

[alnoki]

@bidhan-a will this interact with Mollusk at all?

Not necessarily. But it can be used to build a test harness like Mollusk. For example - here's a test that checks the same program using both Mollusk and the runtime.

@bidhan-a what would be the pros/cons of using Mollusk vs sbpf runtime-style harness?

[bidhan-a]

@bidhan-a will this interact with Mollusk at all?

Not necessarily. But it can be used to build a test harness like Mollusk. For example - here's a test that checks the same program using both Mollusk and the runtime.

@bidhan-a what would be the pros/cons of using Mollusk vs sbpf runtime-style harness?

I think it depends on the use case. sbpf-runtime is a lightweight alternative for testing and debugging without the overhead of a full SVM pipeline, while Mollusk is closer to the actual execution environment.