Update `report_updateLastRead` to not set the sequenceNumber backwards unless specifically told to by the user

[johnmlee101]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Stale update requests are causing people's messages to be marked as unread on accident. This change will prevent stale requests from doing that, while still letting markAsUnread work as intended

Changes:

1. Add a new param setByUser
2. Add a check that prevents the new lastReadSequenceNumber from being less than the previous lastReadSequenceNumber
3. If setByUser is passed, then we ignore that check and allow it to be set to whatever the user chose

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @muttmuure (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[johnmlee101]

cc @kidroca does this look fine for the requirements?

[kidroca]

@johnmlee101 looks good 👍

[melvin-bot]

Triggered auto assignment to @stitesExpensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.