Fix: wait for element to be stable fails on infinite animations (#2711)

[NajoroRabiaza]

Fixes #2711

This PR fixes an issue where actions like click() on elements with infinite CSS animations would not correctly wait for the 10-second timeout and would fail prematurely or proceed unpredictably.

Root Cause
The root cause was a combination of logic flaws in how element stability was checked and how timeouts were communicated back through the Chrome DevTools Protocol (CDP):

isInSamePosition was returning an integer instead of a boolean, confusing the stability logic.

A missing return statement after the initial requestAnimationFrame caused the comparison to happen immediately against the same object.

The 10-second timeout rejected with a primitive false instead of an Error object. In CDP, rejecting with a primitive value swallows the error (resulting in undefined), meaning the Node process never saw the timeout exception.

checkStable was not checking for res.exceptionDetails to propagate the error properly.

Changes Made
Updated isInSamePosition to return a strict boolean (topDiff + leftDiff + bottomDiff + rightDiff === 0).

Added the missing return; statement in waitForElementToBeStable after the first requestAnimationFrame call.

Modified the 10-second timeout to reject with a proper new Error("Element is not stable: still moving after 10000ms").

Added an exceptionDetails check inside checkStable to correctly intercept the timeout error from the browser context and throw it as a standard JavaScript Error in Node.js.

[NivedhaSenthil]

Can you please add an unit test covering this case ?

[NajoroRabiaza]

Yes, I have add two unit tests, so one for when the element is stable and one for the infinite animation case