Fix render speedup after simulation stalls/reconfiguration

[Testtesttestestes]

Motivation

• Visual animation could jump (appearing ~faster) after reinitialization or long stalls because the first frame used a stale timestamp when lastTime was set before async resource loading.
• The animation loop could start/continue after the component effect was cleaned up, causing overlapping/ghost loops and inconsistent timing.
• Kinematic history and reverse-impulse state were preserved across reinitialization, allowing stale motion state to influence the first rendered frames.

Description

• Initialize lastTime to null and set it on the first animation frame to avoid computing a large dt from a stale timestamp (lastTime → null and first-frame assignment).
• Add an isDisposed flag and early returns after async initialization and at the start of the loop to prevent starting or continuing the loop after effect cleanup (isDisposed guard).
• Reset kinematicPrevRef and reverseImpulseRef when the simulation is reinitialized to avoid carrying over stale kinematic state.
• Minor loop and lifecycle adjustments to ensure animation timing and cancellation are robust during reconfigure.

Testing

• Ran npm run build and the production build completed successfully (Vite build finished without errors).

---

Codex Task