fix: (rotation) reset the silent rotation atomically on module disable

Disabling a rotation module mid-aim called cancelTargetRotation with immediate=false, which skips resetRotation while currentRotation != null. The next tick then snapped the silent yaw back to camera at up to 180 deg/tick WHILE the Silent movement-correction was still rewriting motion and sprint flipped on - a one-tick yaw+velocity+sprint discontinuity that GrimAC's movement simulation flags (offset 0.05-0.45 >= the 0.1 immediate-setback threshold), producing the freeze/rubber-band loop even without hitting anyone. Reset atomically (immediate = true) so currentRotation and activeSettings clear in the same tick before movement: onStrafe stops rewriting motion, the packet yaw matches the camera, and sprint reads raw input - velocity and the sent yaw never disagree. Matches the reference build, which keeps velocity decoupled from the silent yaw.

Author: opZywl

src/main/java/net/ccbluex/liquidbounce/features/module/Module.kt

@@ -196,7 +196,12 @@ open class Module(
                     // A broken module-specific cleanup must never leave the module logically
                     // enabled or retain global scheduler/rotation ownership.
                     TickScheduler.cancel(this)
-                    RotationUtils.cancelTargetRotation(this)
+                    // Tear down rotation ownership atomically. With MovementCorrection coupling world
+                    // velocity to the silent server yaw, a smoothed reset snaps the yaw and rewrites
+                    // motion (and can flip sprint) across separate ticks while a target is still live,
+                    // which GrimAC's movement simulation flags -> setback loop. immediate = true resets
+                    // in the same tick, before movement, so velocity and the sent yaw never disagree.
+                    RotationUtils.cancelTargetRotation(this, immediate = true)
                     field = false
                 }
             }