[Bug]: check shouldRevalidation before cancel a loader

[BrianWoolfolk]

Closes #12007

The normal behavior is:
fetcher1.load() gets cancelled if a fetcher2.action() is called, then the fetcher1.load() is called again because of revalidation.

The problem (bug?) is that a cancelled loader would always get revalidated, which means that fetcher1.load() is called two times (even though the first execution is aborted, it could mean a double API fetch).

Suggested behavior:
Check if a loader shouldRevalidate before it gets cancelled (because if not, we can just let it resolve).

This PR is a draft, because this same solution conflicts with things like error-throwing and redirections (and it also breaks some other tests) and wanted to hear your takes on this problem.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 032ba9d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[remix-cla-bot]

Hi @BrianWoolfolk,

Welcome, and thank you for contributing to React Router!

Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once.

You may review the CLA and sign it by adding your name to contributors.yml.

Once the CLA is signed, the CLA Signed label will be added to the pull request.

If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected].

Thanks!

- The Remix team

[remix-cla-bot]

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳