chore(deps): bump core-js from 3.13.1 to 3.22.5

[dependabot]

Bumps core-js from 3.13.1 to 3.22.5.

Changelog

Sourced from core-js's changelog.

3.22.5 - 2022.05.10

• Ensured that polyfilled constructors .prototype is non-writable
• Ensured that polyfilled methods .prototype is not defined
• Added detection and fix of a V8 ~ Chrome <103 bug of struturedClone that returns null if cloned object contains multiple references to one error

3.22.4 - 2022.05.03

• Ensured proper .length of polyfilled functions even in compressed code (excepting some ancient engines)
• Ensured proper .name of polyfilled accessors (excepting some ancient engines)
• Ensured proper source / ToString conversion of polyfilled accessors
• Actualized Rhino compat data
• Refactoring

3.22.3 - 2022.04.28

• Added a fix for FF99+ Array.prototype.includes broken on sparse arrays

3.22.2 - 2022.04.21

• Fixed URLSearchParams in IE8- that was broken in the previous release
• Fixed __lookupGetter__ entries

3.22.1 - 2022.04.20

• Improved some cases of RegExp flags handling
• Prevented experimental warning in NodeJS ~ 18.0 on detection fetch API
• Added NodeJS 18.0 compat data

3.22.0 - 2022.04.15

• Change Array by copy proposal:
  • Moved to Stage 3, March TC39 meeting
  • Disabled forced replacement and added /actual/ entry points for methods from this proposal
  • Array.prototype.toSpliced throws a TypeError instead of RangeError if the result length is more than MAX_SAFE_INTEGER, proposal-change-array-by-copy/70
• Added some more atob / btoa fixes:
  • NodeJS <17.9 atob does not ignore spaces, node/42530
  • Actual NodeJS atob does not validate encoding, node/42646
  • FF26- implementation does not properly convert argument to string
  • IE / Edge <16 implementation have wrong arity
• Added /full/ namespace as the replacement for /features/ since it's more descriptive in context of the rest namespaces (/es/ ⊆ /stable/ ⊆ /actual/ ⊆ /full/)
• Avoided propagation of removed parts of proposals to upper stages. For example, %TypedArray%.prototype.groupBy was removed from the Array grouping proposal a long time ago. We can't completely remove this method since it's a breaking change. But this proposal has been promoted to stage 3 - so the proposal should be promoted without this method, this method should not be available in /actual/ entries - but it should be available in early-stage entries to avoid breakage.
• Significant internal refactoring and splitting of modules (but without exposing to public API since it will be a breaking change - it will be exposed in the next major version)
• Bug fixes:
  • Fixed work of non-standard V8 Error features with wrapped Error constructors, #1061
  • null and undefined allowed as the second argument of structuredClone, #1056
• Tooling:
  • Stabilized proposals are filtered out from the core-js-compat -> core-js-builder -> core-js-bundle output. That mean that if the output contains, for example, es.object.has-own, the legacy reference to it, esnext.object.has-own, no longer added.
  • Aligned modules filters of core-js-builder and core-js-compat, now it's modules and exclude options
  • Added support of entry points, modules, regexes, and arrays of them to those filters
  • Missed targets option of core-js-compat means that the targets filter just will not be applied, so the result will contain modules required for all possible engines
• Compat data:
  • .stack property on DOMException marked as supported from Deno 1.15
  • Added Deno 1.21 compat data mapping
  • Added Electron 19.0 and updated 18.0 compat data mapping
  • Added Samsung Internet 17.0 compat data mapping

... (truncated)

Commits

• f1b4f76 3.22.5
• 951124c add links to releases to the changelog
• c53c1b2 update dependencies
• ef26f65 ensure proper .prototype of polyfills
• 666631a increase DEV_NODE_VERSIONS to ^16.13
• 4c64845 first Node 16 LTS was 16.13
• a946ca4 drop node 14 from ci
• 8e8f221 replace lerna with npm workspaces
• 7a2ebfa a stylistic change
• e7f3df4 update dependencies
• 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 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 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)