build(deps): Bump react-router from 6.16.0 to 6.20.0 in /api-editor/gui (#1471)

Bumps
[react-router](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router)
from 6.16.0 to 6.20.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/remix-run/react-router/releases">react-router's
releases</a>.</em></p>
<blockquote>
<h2>v6.20.0</h2>
<p>Release notes are stored in the <code>CHANGELOG.md</code> file:</p>
<p><a
href="https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6200">https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6200</a></p>
<h2>v6.19.0</h2>
<p>Release notes are stored in the <code>CHANGELOG.md</code> file:</p>
<p><a
href="https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6190">https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6190</a></p>
<h2>v6.18.0</h2>
<h2>Minor Changes</h2>
<h3>New Fetcher APIs</h3>
<p>Per this <a
href="https://github.com/remix-run/remix/discussions/7698">RFC</a>,
we've introduced some new APIs that give you more granular control over
your fetcher behaviors. (<a
href="https://redirect.github.com/remix-run/react-router/pull/10960">#10960</a>)</p>
<ul>
<li>You may now specify your own fetcher identifier via
<code>useFetcher({ key: string })</code>, which allows you to access the
same fetcher instance from different components in your application
without prop-drilling</li>
<li>Fetcher keys are now exposed on the fetchers returned from
<code>useFetchers</code> so that they can be looked up by
<code>key</code></li>
<li><code>Form</code> and <code>useSumbit</code> now support optional
<code>navigate</code>/<code>fetcherKey</code> props/params to allow
kicking off a fetcher submission under the hood with an optionally
user-specified <code>key</code>
<ul>
<li><code>&lt;Form method=&quot;post&quot; navigate={false}
fetcherKey=&quot;my-key&quot;&gt;</code></li>
<li><code>submit(data, { method: &quot;post&quot;, navigate: false,
fetcherKey: &quot;my-key&quot; })</code></li>
<li>Invoking a fetcher in this way is ephemeral and stateless</li>
<li>If you need to access the state of one of these fetchers, you will
need to leverage <code>useFetchers()</code> or <code>useFetcher({ key
})</code> to look it up elsewhere</li>
</ul>
</li>
</ul>
<h3>Persistence Future Flag (<code>future.v7_fetcherPersist</code>)</h3>
<p>Per the same <a
href="https://github.com/remix-run/remix/discussions/7698">RFC</a> as
above, we've introduced a new <code>future.v7_fetcherPersist</code> flag
that allows you to opt-into the new fetcher persistence/cleanup
behavior. Instead of being immediately cleaned up on unmount, fetchers
will persist until they return to an <code>idle</code> state. This makes
pending/optimistic UI <em>much</em> easier in scenarios where the
originating fetcher needs to unmount. (<a
href="https://redirect.github.com/remix-run/react-router/pull/10962">#10962</a>)</p>
<ul>
<li>This is sort of a long-standing bug fix as the
<code>useFetchers()</code> API was always supposed to only reflect
<strong>in-flight</strong> fetcher information for pending/optimistic UI
-- it was not intended to reflect fetcher data or hang onto fetchers
after they returned to an <code>idle</code> state</li>
<li>Keep an eye out for the following specific behavioral changes when
opting into this flag and check your app for compatibility:
<ul>
<li>Fetchers that complete <em>while still mounted</em> will no longer
appear in <code>useFetchers()</code> after completion - they served no
purpose in there since you can access the data via
<code>useFetcher().data</code></li>
<li>Fetchers that previously unmounted <em>while in-flight</em> will not
be immediately aborted and will instead be cleaned up once they return
to an <code>idle</code> state
<ul>
<li>They will remain exposed via <code>useFetchers</code> while
in-flight so you can still access pending/optimistic data after
unmount</li>
<li>If a fetcher is no longer mounted when it completes, then it's
result will not be post processed - e.g., redirects will not be followed
and errors will not bubble up in the UI</li>
<li>However, if a fetcher was re-mounted elsewhere in the tree using the
same <code>key</code>, then it's result will be processed, even if the
originating fetcher was unmounted</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3>Other Minor Changes</h3>
<ul>
<li>Add support for optional path segments in <code>matchPath</code> (<a
href="https://redirect.github.com/remix-run/react-router/pull/10768">#10768</a>)</li>
</ul>
<h2>Patch Changes</h2>
<ul>
<li>Fix the <code>future</code> prop on <code>BrowserRouter</code>,
<code>HashRouter</code> and <code>MemoryRouter</code> so that it accepts
a <code>Partial&lt;FutureConfig&gt;</code> instead of requiring all
flags to be included (<a
href="https://redirect.github.com/remix-run/react-router/pull/10962">#10962</a>)</li>
<li>Fix <code>router.getFetcher</code>/<code>router.deleteFetcher</code>
type definitions which incorrectly specified <code>key</code> as an
optional parameter (<a
href="https://redirect.github.com/remix-run/react-router/pull/10960">#10960</a>)</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/remix-run/react-router/compare/[email protected]@6.18.0"><code>6.17.0...6.18.0</code></a></p>
<h2>v6.17.0</h2>
<h2>Minor Changes</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/remix-run/react-router/blob/main/packages/react-router/CHANGELOG.md">react-router's
changelog</a>.</em></p>
<blockquote>
<h2>6.20.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>Export the <code>PathParam</code> type from the public API (<a
href="https://redirect.github.com/remix-run/react-router/pull/10719">#10719</a>)</li>
</ul>
<h3>Patch Changes</h3>
<ul>
<li>Fix bug with <code>resolveTo</code> in splat routes (<a
href="https://redirect.github.com/remix-run/react-router/pull/11045">#11045</a>)
<ul>
<li>This is a follow up to <a
href="https://redirect.github.com/remix-run/react-router/pull/10983">#10983</a>
to handle the few other code paths using
<code>getPathContributingMatches</code></li>
<li>This removes the <code>UNSAFE_getPathContributingMatches</code>
export from <code>@remix-run/router</code> since we no longer need this
in the <code>react-router</code>/<code>react-router-dom</code>
layers</li>
</ul>
</li>
<li>Updated dependencies:
<ul>
<li><code>@remix-run/[email protected]</code></li>
</ul>
</li>
</ul>
<h2>6.19.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>Add <code>unstable_flushSync</code> option to
<code>useNavigate</code>/<code>useSumbit</code>/<code>fetcher.load</code>/<code>fetcher.submit</code>
to opt-out of <code>React.startTransition</code> and into
<code>ReactDOM.flushSync</code> for state updates (<a
href="https://redirect.github.com/remix-run/react-router/pull/11005">#11005</a>)</li>
<li>Remove the <code>unstable_</code> prefix from the <a
href="https://reactrouter.com/en/main/hooks/use-blocker"><code>useBlocker</code></a>
hook as it's been in use for enough time that we are confident in the
API. We do not plan to remove the prefix from
<code>unstable_usePrompt</code> due to differences in how browsers
handle <code>window.confirm</code> that prevent React Router from
guaranteeing consistent/correct behavior. (<a
href="https://redirect.github.com/remix-run/react-router/pull/10991">#10991</a>)</li>
</ul>
<h3>Patch Changes</h3>
<ul>
<li>
<p>Fix <code>useActionData</code> so it returns proper contextual action
data and not <em>any</em> action data in the tree (<a
href="https://redirect.github.com/remix-run/react-router/pull/11023">#11023</a>)</p>
</li>
<li>
<p>Fix bug in <code>useResolvedPath</code> that would cause
<code>useResolvedPath(&quot;.&quot;)</code> in a splat route to lose the
splat portion of the URL path. (<a
href="https://redirect.github.com/remix-run/react-router/pull/10983">#10983</a>)</p>
<ul>
<li>⚠️ This fixes a quite long-standing bug specifically for
<code>&quot;.&quot;</code> paths inside a splat route which incorrectly
dropped the splat portion of the URL. If you are relative routing via
<code>&quot;.&quot;</code> inside a splat route in your application you
should double check that your logic is not relying on this buggy
behavior and update accordingly.</li>
</ul>
</li>
<li>
<p>Updated dependencies:</p>
<ul>
<li><code>@remix-run/[email protected]</code></li>
</ul>
</li>
</ul>
<h2>6.18.0</h2>
<h3>Patch Changes</h3>
<ul>
<li>Fix the <code>future</code> prop on <code>BrowserRouter</code>,
<code>HashRouter</code> and <code>MemoryRouter</code> so that it accepts
a <code>Partial&lt;FutureConfig&gt;</code> instead of requiring all
flags to be included. (<a
href="https://redirect.github.com/remix-run/react-router/pull/10962">#10962</a>)</li>
<li>Updated dependencies:
<ul>
<li><code>@remix-run/[email protected]</code></li>
</ul>
</li>
</ul>
<h2>6.17.0</h2>
<h3>Patch Changes</h3>
<ul>
<li>Fix <code>RouterProvider</code> <code>future</code> prop type to be
a <code>Partial&lt;FutureConfig&gt;</code> so that not all flags must be
specified (<a
href="https://redirect.github.com/remix-run/react-router/pull/10900">#10900</a>)</li>
<li>Updated dependencies:
<ul>
<li><code>@remix-run/[email protected]</code></li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/remix-run/react-router/commit/3cc38eac4753702a9a8a1fe239e2138d63ac6cc5"><code>3cc38ea</code></a>
chore: Update version for release (<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/11050">#11050</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/1e026b6f1ac34a774b4f77e5e3696251e8f79940"><code>1e026b6</code></a>
chore: Update version for release (pre) (<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/11047">#11047</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/58d421fc4c592661a68dea59edc507fc4668ba5d"><code>58d421f</code></a>
Fix other code paths for resolveTo from a splat route (<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/11045">#11045</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/f320378b5145f59bb266a35a7655b563f712daef"><code>f320378</code></a>
Add additional test case for <a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/10983">#10983</a></li>
<li><a
href="https://github.com/remix-run/react-router/commit/a48c43c8118bbf75b23b3ee748648bb3ee4d688e"><code>a48c43c</code></a>
feat: export <code>PathParam</code> type (<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/10719">#10719</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/dcf0c2a85aac3a78059a287ea478ff12adcb6a2d"><code>dcf0c2a</code></a>
chore: Update version for release (<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/11035">#11035</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/7b1bd10a1f0d21dd303ae7346bd555616ca2a2fa"><code>7b1bd10</code></a>
chore: Update version for release (pre) (<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/11026">#11026</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/39854ce7a82d24b60ff2ccbd84d46fa14dbf5b62"><code>39854ce</code></a>
Fix useAcrtionData so it only returns the contextual route action data
(<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/11023">#11023</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/1193ae5e28124cc163bb3c4f5478cf057bb2f087"><code>1193ae5</code></a>
Add unstable_flushSync option (<a
href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router/issues/11005">#11005</a>)</li>
<li><a
href="https://github.com/remix-run/react-router/commit/fe066bd4641a17142e73569b116c0236d8c9e1d7"><code>fe066bd</code></a>
Fix issues with useFormAction/useResolvedPath for dot paths in
param/splat ro...</li>
<li>Additional commits viewable in <a
href="https://github.com/remix-run/react-router/commits/[email protected]/packages/react-router">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=react-router&package-manager=npm_and_yarn&previous-version=6.16.0&new-version=6.20.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

api-editor/gui/package-lock.json

@@ -35,7 +35,7 @@
         "react-icons": "^4.10.1",
         "react-markdown": "^8.0.7",
         "react-redux": "^8.1.1",
-        "react-router": "^6.16.0",
+        "react-router": "^6.20.0",
         "react-router-dom": "^6.14.1",
         "react-syntax-highlighter": "^15.5.0",
         "react-window": "^1.8.9",