Fix: Post title caret position issue

[Kallyan01]

What?

See: #64724

Why?

Previously we were not maintaining any caret position history stacks so predicting caret positions on undo/redo was not possible .

How?

• Used a history array which records the caret positions on different onChange events .
• Captured different key strokes to listen to undo and redo events .

Testing Instructions

Testing Instructions for Keyboard

• Add a new post or page.
• Select the Title block and enter a title.
• Paste additional text into the end of the field.
• Undo the paste with Cmd+z/Ctrl+z (using the editor toolbar Undo button changes focus from the field, so is n/a).
• Observe the location of the caret after undo ( | caret is moved to start of the deleted text).
• Without clicking or repositioning the caret, re-paste into the field with Cmd+v/Ctrl+v.
• Observe where the pasted text is inserted ( | text is inserted at end of field with updated caret position ).

Screenshots or screencast

Before

Screen.Recording.2024-12-16.at.4.22.47.PM.mov

After

Screen.Recording.2024-12-16.at.4.16.45.PM.mov

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @Kallyan01! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Kallyan01 <[email protected]>
Co-authored-by: Mamaduka <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Mamaduka]

Posted a general comment in the issue - #64724 (comment); let's continue the discussion there.

@Kallyan01, the trunk on your fork seems a bit out of sync. Do you mind rebasing this atop the lastest trunk from "upstream"?