fix: setCaretTimeout checks

[csantos1113]

Describe the change

Fixes #811

I'm opening this PR as an attempt to resolve jest + testing-library issue reported in #811.

I have an open question on that issue #811 (comment) where I wondered why el.selectionStart !== el.selectionEnd existed; but after a lot of thinking I cannot see a reason for it

My thinking

selectionStart and selectionEnd will always be the same when the caret is placed and nothing is selected:

Screen.Recording.2023-11-21.at.9.32.13.PM.mov

so el.selectionStart !== el.selectionEnd will only happen if the user have text selected:

Screen.Recording.2023-11-21.at.9.32.38.PM.mov

which differs from the intention described by the inline comment that is in the code:

    /* setting caret position within timeout of 0ms is required for mobile chrome,
    otherwise browser resets the caret position after we set it
    We are also setting it without timeout so that in normal browser we don't see the flickering */

But please let me know if I've missed something else on my analysis 🙏

[csantos1113]

Hey @s-yadav - I'm gently pinging you for when you get a chance to review this PR. Thank you!

[csantos1113]

@s-yadav 👋 when you get a chance, this would be much appreciated!

[s-yadav]

Yes, the selectionStart !== selectionEnd mostly looks unintentional. the check with caretPos, is correct.
I will see if it can be accompanied by a test as this was mostly a side-effect of not having a test.

Update:
Added the test from your codesandbox. Thanks