feat: move next frame and next world update into managed side

[roflmuffin]

Move NextFrame queue to managed .NET side

During extensive testing of NextFrame and related scheduling code, I benchmarked using a .NET ConcurrentQueue<T> instead of the current C++ concurrent queue implementation.

Results

• Native C++ approach: Queuing and resolving 100,000 NextFrame tasks took ~300ms on average (mainly due to P/Invoke overhead & FunctionReference memory allocations)
• Managed .NET approach: The same workload completed in 5–20ms (variance depends on where in the frame the benchmark was queued)

This is roughly a 50x improvement by moving the queue storage to the .NET side and having a managed listener drain the queue each frame.