chore(deps-dev): bump react-router from 6.20.1 to 6.21.0

[dependabot]

Bumps react-router from 6.20.1 to 6.21.0.

Release notes

Sourced from react-router's releases.

v6.21.0

Release notes are stored in the CHANGELOG.md file:

https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6210

Changelog

Sourced from react-router's changelog.

6.21.0

Minor Changes

• Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#11087)

  This fix was originally added in #10983 and was later reverted in #11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #11052)

  The Bug The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

  The Background This decision was originally made thinking that it would make the concept of nested different sections of your apps in <Routes> easier if relative routing would replace the current splat:

  <BrowserRouter>
    <Routes>
      <Route path="/" element={<Home />} />
      <Route path="dashboard/*" element={<Dashboard />} />
    </Routes>
  </BrowserRouter>

  Any paths like /dashboard, /dashboard/team, /dashboard/projects will match the Dashboard route. The dashboard component itself can then render nested <Routes>:

  function Dashboard() {
    return (
      <div>
        <h2>Dashboard</h2>
        <nav>
          <Link to="/">Dashboard Home</Link>
          <Link to="team">Team</Link>
          <Link to="projects">Projects</Link>
        </nav>
    &lt;Routes&gt;
      &lt;Route path=&quot;/&quot; element={&lt;DashboardHome /&gt;} /&gt;
      &lt;Route path=&quot;team&quot; element={&lt;DashboardTeam /&gt;} /&gt;
      &lt;Route path=&quot;projects&quot; element={&lt;DashboardProjects /&gt;} /&gt;
    &lt;/Routes&gt;
  &lt;/div&gt;
  
  );
  }

  Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the Dashboard as its own independent app, or embed it into your large app without making any changes to it.

  The Problem

... (truncated)

Commits

• 69ba50e chore: Update version for release (#11114)
• ea0ffee chore: Update version for release (pre) (#11095)
• fe3c071 Slight refactor to partial hydration to leverage state.initialized properly (...
• 373b30c chore: Update version for release (pre) (#11091)
• 56b2944 chore: Update version for release (pre) (#11090)
• 558d793 Fix plumbing of future prop
• ee5fcd5 Generate release notes
• ddc2b94 chore: Update version for release (pre) (#11089)
• 149ad65 Add future.v7_relativeSplatPath flag (#11087)
• d04c541 Fix tests from conflicting PRs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @mdn-bot.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[mdn-bot]

@dependabot squash and merge

[dependabot]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[dependabot]

Looks like react-router is up-to-date now, so this is no longer needed.