Repository: create-react-app
Issue: react-app-polyfill does not polyfill String.prototype.replaceAll
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

`react-app-polyfill` does not polyfill `String.prototype.replaceAll`.

### Environment

<!--
  To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
  This enables the maintainers quickly reproduce the issue and give feedback.

  Run the following command in your React app's folder in terminal.
  Note: The result is copied to your clipboard directly.

  `npx create-react-app --info`

  Paste the output of the command in the section below.
-->

```bash
Environment Info:

  current version of create-react-app: 5.0.1
  running from C:\Users\listl\scoop\persist\nodejs\cache\_npx\c67e74de0542c87c\node_modules\create-react-app

  System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
  Binaries:
    Node: 18.8.0 - ~\scoop\apps\nodejs\current\node.EXE
    Yarn: Not Found
    npm: 8.18.0 - ~\scoop\apps\nodejs\current\npm.CMD
  Browsers:
    Chrome: 81.0.4044.92
    Edge: Spartan (44.19041.1266.0), Chromium (104.0.1293.70)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    react-scripts: 5.0.1 => 5.0.1
  npmGlobalPackages:
    create-react-app: Not Found
```

### Steps to reproduce

<!--
  How would you describe your issue to someone who doesn’t know you or your project?
  Try to write a sequence of steps that anybody can repeat to see the issue.
-->

1. run `npx create-react-app test --template typescript`
2. Add `import "react-app-polyfill/stable";` to the first line of `src/index.tsx`
3. Add `"chorme > 80"` to `browserlists.production` of `package.json`
4. Change the App.tsx file to
```tsx
function App() {
  return <>{"app".replaceAll("a", "A")}</>;
}

export default App;
```
5. run `npm start`


### Expected behavior


![image](https://user-images.githubusercontent.com/34062491/187590504-354382fc-2709-4b80-9d91-59ef5fec014e.png)

It displays "App". Screenshotted from Edge 104

### Actual behavior

<!--
  Did something go wrong?
  Is something broken, or not behaving as you expected?
  Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
-->
![image](https://user-images.githubusercontent.com/34062491/187590733-c04c4580-2d2f-45fa-a999-f7ad52b410d3.png)

`"app".replaceAll` is not a function. Screenshotted from Chrome 81, for Chrome started supporting `String.prototype.replaceAll` from 85
![image](https://user-images.githubusercontent.com/34062491/187590987-0d6d43a5-44bd-4627-8603-4ba6f76d97c0.png)


### Reproducible demo
[test.zip](https://github.com/facebook/create-react-app/files/9458385/test.zip)

<!--
  If you can, please share a project that reproduces the issue.
  This is the single most effective way to get an issue fixed soon.

  There are two ways to do it:

    * Create a new app and try to reproduce the issue in it.
      This is useful if you roughly know where the problem is, or can’t share the real code.

    * Or, copy your app and remove things until you’re left with the minimal reproducible demo.
      This is useful for finding the root cause. You may then optionally create a new project.

  This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
  Once you’re done, push the project to GitHub and paste the link to it below:
-->

<!--
  What happens if you skip this step?

  We will try to help you, but in many cases it is impossible because crucial
  information is missing. In that case we'll tag an issue as having a low priority,
  and eventually close it if there is no clear direction.

  We still appreciate the report though, as eventually somebody else might
  create a reproducible example for it.

  Thanks for helping us help you!
-->

### Others
I found the same question at [stackoverflow](https://stackoverflow.com/questions/65023675/) and it seems to be an old bug that has not yet been fixed