Update dependency react-redux to v8.1.0 (#298)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [react-redux](https://togithub.com/reduxjs/react-redux) | [`8.0.5` ->
`8.1.0`](https://renovatebot.com/diffs/npm/react-redux/8.0.5/8.1.0) |
[![age](https://badges.renovateapi.com/packages/npm/react-redux/8.1.0/age-slim)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://badges.renovateapi.com/packages/npm/react-redux/8.1.0/adoption-slim)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://badges.renovateapi.com/packages/npm/react-redux/8.1.0/compatibility-slim/8.0.5)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://badges.renovateapi.com/packages/npm/react-redux/8.1.0/confidence-slim/8.0.5)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>reduxjs/react-redux</summary>

###
[`v8.1.0`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.1.0)

[Compare
Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.7...v8.1.0)

This **feature release** adds new development-mode safety checks for
common errors (like poorly-written selectors), adds a workaround to fix
crash errors when React-Redux hooks are imported into React Server
Component files, and updates our hooks API docs page with improved
explanations and updated links.

#### Changelog

##### Development Mode Checks for `useSelector`

We've had a number of users tell us over time that it's common to
accidentally write selectors that have bad behavior and cause
performance issues. The most common causes of this are either selectors
that unconditionally return a new reference (such as `state =>
state.todos.map()` without any memoization ), or selectors that actually
return the *entire* root state ( `state => state` ).

We've updated `useSelector` to add safety checks in development mode
that warn if these incorrect behaviors are detected:

- Selectors will be called twice with the same inputs, and `useSelector`
will warn if the results are different references
- `useSelector` will warn if the selector result is actually the entire
root `state`

By default, **these checks only run *once* the first time `useSelector`
is called**. This should provide a good balance between detecting
possible issues, and keeping development mode execution performant
without adding many unnecessary extra selector calls.

If you want, you can configure this behavior globally by passing the
enum flags directly to `<Provider>`, or on a per-`useSelector` basis by
passing an options object as the second argument:

```ts
// Example: globally configure the root state "noop" check to run every time
<Provider store={store} noopCheck="always">
  {children}
</Provider>
```

```ts
// Example: configure `useSelector` to specifically run the reference checks differently:
function Component() {
  // Disable check entirely for this selector
  const count = useSelector(selectCount, { stabilityCheck: 'never' })
  // run once (default)
  const user = useSelector(selectUser, { stabilityCheck: 'once' })
  // ...
}
```

This goes along with the similar safety checks we've added to [Reselect
v5
alpha](https://togithub.com/reduxjs/reselect/releases/tag/v5.0.0-alpha.2)
as well.

##### Context Changes

We're still trying to work out how to properly use Redux and React
Server Components together. One possibility is using RTK Query's
`createApi` to define data fetching endpoints, and using the generated
thunks to fetch data in RSCs, but it's still an open question.

However, users have reported that merely importing *any* React-Redux API
in an RSC file causes a crash, because `React.createContext` is not
defined in RSC files. RTKQ's React-specific `createApi` entry point
imports React-Redux, so it's been unusable in RSCs.

This release adds a workaround to fix that issue, by using a proxy
wrapper around our singleton `ReactReduxContext` instance and lazily
creating that instance on demand. In testing, this appears to both
continue to work in all unit tests, *and* fixes the import error in an
RSC environment. We'd appreciate further feedback in case this change
does cause any issues for anyone!

We've also tweaked the internals of the hooks to do checks for correct
`<Provider>` usage when using a custom context, same as the default
context checks.

##### Docs Updates

We've cleaned up some of the Hooks API reference page, and updated links
to the React docs.

#### What's Changed

- check for Provider even when using custom context by
[@&#8203;EskiMojo14](https://togithub.com/EskiMojo14) in
[https://github.com/reduxjs/react-redux/pull/1990](https://togithub.com/reduxjs/react-redux/pull/1990)
- Add a stability check, to see if selector returns stable result when
called with same parameters. by
[@&#8203;EskiMojo14](https://togithub.com/EskiMojo14) in
[https://github.com/reduxjs/react-redux/pull/2000](https://togithub.com/reduxjs/react-redux/pull/2000)
- Add an E2E-ish test that verifies behavior when imported into RSCs by
[@&#8203;markerikson](https://togithub.com/markerikson) in
[https://github.com/reduxjs/react-redux/pull/2030](https://togithub.com/reduxjs/react-redux/pull/2030)
- lazily create Context for RSC compat by
[@&#8203;phryneas](https://togithub.com/phryneas) in
[https://github.com/reduxjs/react-redux/pull/2025](https://togithub.com/reduxjs/react-redux/pull/2025)
- Add warning for selectors that return the entire state by
[@&#8203;EskiMojo14](https://togithub.com/EskiMojo14) in
[https://github.com/reduxjs/react-redux/pull/2022](https://togithub.com/reduxjs/react-redux/pull/2022)

**Full Changelog**:
reduxjs/react-redux@v8.0.7...v8.1.0

###
[`v8.0.7`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.7)

[Compare
Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.6...v8.0.7)

This release updates the peer dependencies to accept Redux Toolkit, and
accept the ongoing RTK and Redux core betas as valid peer deps.

> **Note**: These changes were initially in 8.0.6, but that had a typo
in the peer deps that broke installation. Sorry!

#### What's Changed

- Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by
[@&#8203;markerikson](https://togithub.com/markerikson) in
[https://github.com/reduxjs/react-redux/pull/2017](https://togithub.com/reduxjs/react-redux/pull/2017)
- [`d45204f`](https://togithub.com/reduxjs/react-redux/commit/d45204f) :
Fix broken RTK peer dep

**Full Changelog**:
reduxjs/react-redux@v8.0.5...v8.0.7

###
[`v8.0.6`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.6)

[Compare
Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.5...v8.0.6)

\~~This release updates the peer dependencies to accept Redux Toolkit,
and accept the ongoing RTK and Redux core betas as valid peer deps.~~

**This release has a peer deps typo that breaks installation - please
use 8.0.7 instead !**

#### What's Changed

- Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by
[@&#8203;markerikson](https://togithub.com/markerikson) in
[https://github.com/reduxjs/react-redux/pull/2017](https://togithub.com/reduxjs/react-redux/pull/2017)

**Full Changelog**:
reduxjs/react-redux@v8.0.5...v8.0.6

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://app.renovatebot.com/dashboard#github/ASVGay/the-rhapsodies).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS4xMTUuMiIsInVwZGF0ZWRJblZlciI6IjM1LjExNS4yIiwidGFyZ2V0QnJhbmNoIjoiZGV2In0=-->