fix: (rotation) clear input/rotation history on immediate teardown to stop toggle-time Grim Simulation

The atomic disable teardown (immediate cancel) reset the rotation but kept the stale modifiedInput and server-rotation history. On the tick right after a module toggles off, GrimAC still reconstructed movement from the scaffold/silent-modified input against the now-real sent yaw, producing a Simulation offset (the 'sometimes flags on enable/disable' report). Pass resetHistory=immediate so an immediate teardown also reseeds lastRotations/actualServerRotation from the real rotation and clears modifiedInput, matching the reference build which has no such coupling.

Author: opZywl

src/main/java/net/ccbluex/liquidbounce/utils/rotation/RotationUtils.kt

@@ -695,7 +695,10 @@ object RotationUtils : MinecraftInstance, Listenable {
         resetTicks = 0
 
         if (immediate || currentRotation == null) {
-            resetRotation()
+            // On an immediate teardown (module disable) also clear the input/rotation history so the
+            // next tick's movement prediction carries no stale scaffold/silent modifiedInput or
+            // server-rotation, which otherwise desyncs GrimAC's Simulation on the toggle tick.
+            resetRotation(resetHistory = immediate)
         }
 
         return true