fix(react-router-dom): make useFetcher stable

[vaynevayne]

resolve remix-run/remix#6072

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2f62cd8

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 @vaynevayne,

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 hello@remix.run.

Thanks!

- The Remix team

[remix-cla-bot]

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

[brophdawg11]

This would break fetchers quite badly because the fetcherKey never changes so you'd never see the results of your fetches. Instead the fetcher data and state inside the router is what changes and is why our fetcherWithComponents is memoized with fetcher as a dependency.

fetcher.submit was stabilized in #10336 which will be included in the next release.