This pull request addresses an issue in the jQuery Deferred implementation where an infinite loop was being triggered when the .then() statement was executed after an animation completion. This issue occurred because the state was being continuously set to "resolved," leading to unintended behavior and performance degradation.

Changes Made:

1. Introduced Flag to Track State Resolution:

• A flag isResolvedOrRejected was introduced to track whether the deferred state has already been set to either "resolved" or "rejected." This ensures that once the state changes, further state transitions do not occur, preventing continuous updates.

2. State Change Condition:

• Modified the code to check if the state has already been set to "resolved" or "rejected" before triggering another state change. This prevents redundant calls to resolveWith and fireWith.

3. Controlled Execution of .then() Handlers:

• Ensured that the .then() handlers (which are responsible for resolving the deferred promise) are only executed once when the animation completes, thus preventing the infinite loop of state changes.

4.Smoother Animation Execution:

• By eliminating the redundant state changes, the animation now executes smoothly without interruptions caused by the repeated triggering of state transitions.

Testing:

• Verified that after an animation completes, the resolved state is only set once, and the animation continues without issues.
• Ensured that the animation behavior is smooth without any unexpected state changes.

Fixes #5534