Edit/Delete with Checkpoints

[liwilliam2021]

We now make a checkpoint after every user message so when a user edits a user message. Now when a user has checkpoints enabled, upon deleting or editing a message they are asked if they would like to restore the checkpoint right before the message was sent

Feature Loom: https://www.loom.com/share/a810f38550524e079c3d8c6eb8c53ce5

Edge cases + stress testing Loom: https://www.loom.com/share/28e56e97da944cc18144b9c92594b8e5
Follow Up question editing Loom: https://www.loom.com/share/8f6da376cbb842219ba4eb9aa7956b04
Checkpoints not enabled Loom: https://www.loom.com/share/0fdfde900c494239a16ac19ad26a597f

Fixes #4703

---

Important

This pull request adds a feature for restoring checkpoints when editing or deleting messages, including UI updates and internationalization support.

• Behavior:
  • Adds checkpoint restoration feature for message edits and deletions in ChatRow.tsx and ChatView.tsx.
  • Prompts users with CheckpointRestoreDialog to confirm restoration of checkpoints.
• UI Components:
  • Introduces CheckpointRestoreDialog.tsx for handling user confirmations on checkpoint restoration.
  • Updates ChatRow.tsx to include edit and delete buttons with checkpoint options.
  • Modifies ChatView.tsx to manage message visibility and checkpoint prompts.
• Internationalization:
  • Updates i18n files across multiple languages to include translations for new checkpoint-related dialog options.

^{This description was created by for 15ce9e3. You can customize this summary. It will automatically update as commits are pushed.}

[liwilliam2021]

This change was made to make timestamping against checkpoints easier-- as far I as I can see removing the buffer doesn't break anything

[daniel-lxs]

For future consideration: The state transitions during checkpoint restoration (task running → aborting → restoring → reinitialized → processing pending edits) could benefit from a formal state machine implementation to make the flow more explicit.

LGTM.