[WEB-4592] Fix patient list stale-overwrite race under slow network

[clintonium-119]

WEB-4592 Fix patient list stale-overwrite race under slow network

When multiple fetchPatientsForClinic dispatches are in flight
simultaneously, an older response arriving last would overwrite the
newer one's correctly-filtered result, then flipping to the unfiltered
set.

[Copilot]

Pull request overview

This PR addresses a stale-overwrite race in the clinic patients fetch flow by ensuring that when multiple fetchPatientsForClinic requests are in flight, only the most recently-dispatched request is allowed to update Redux state.

Changes:

• Add a monotonic request sequence guard to fetchPatientsForClinic to ignore stale success/failure callbacks.
• Add unit tests covering stale success and stale failure response abandonment behavior.
• Bump package version from 1.95.3-rc.1 to 1.95.3-rc.2.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
app/redux/actions/async.js	Introduces a request sequence counter to abandon stale getPatientsForClinic responses.
test/unit/redux/actions/async.test.js	Adds regression tests ensuring stale responses don’t dispatch SUCCESS/FAILURE.
package.json	Increments release candidate version.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[henry-tp]

Not a fan of the counter method but it resolves the issue we have for now and I can't come up with an immediate alternative. We should make an effort to move to the fetching away from platform-client as soon as we can.