recent-conversations: Not completely rerender for a single message

[lumpleme]

Updates recent_view_ui.process_messages to have a check before rerendering, so rerendering one single message can be done with inplace_rerender instead of complete_rerender.

Fixes: #23638

[zulipbot]

Hello @lumpleme, it seems like you have referenced #23638 in your pull request description, but you have not referenced them in your commit message description(s). Referencing an issue in a commit message automatically closes the corresponding issue when the commit is merged, which makes the issue tracker easier to manage.

Please run git commit --amend in your command line client to amend your commit message description with Fixes #23638..

An example of a correctly-formatted commit:

commit fabd5e450374c8dde65ec35f02140383940fe146
Author: zulipbot
Date:   Sat Mar 18 13:42:40 2017 -0700

    pull requests: Check PR commits reference when issue is referenced.

    Fixes #51.

To learn how to write a great commit message, please refer to our guide.

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: web/src/recent_view_ui.js

Function	Unhandled Issue
process_messages	RangeError: Invalid time value get_localized_date... Event Count: 33 Affected Users: 51
process_messages	RangeError: date value is not finite in DateTimeFormat format() update_load_more_banner(src/... Event Count: 5 Affected Users: 1

---

_{Did you find this useful? React with a 👍 or 👎}

[amanagr]

We also need to modify inplce_rerender fix the current position of the topic.

[zulipbot]

Heads up @lumpleme, we just merged some commits that conflict with the changes you made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the upstream/main branch and resolve your pull request's merge conflicts accordingly.