fix(deps): update dependency core-js to v3.32.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
core-js	3.31.1 -> 3.32.1

---

Release Notes

zloirock/core-js (core-js)

v3.32.1

Compare Source

• Fixed some cases of IEEE754 rounding, #​1279, thanks @​petamoriken
• Prevented injection process polyfill to core-js via some bundlers or esm.sh, #​1277
• Some minor fixes and stylistic changes
• Compat data improvements:
  • Promise.withResolvers marked as supported from Bun 0.7.1
  • Added Opera Android 77 compat data mapping
  • Updated Electron 27 compat data mapping

v3.32.0

Compare Source

• Array grouping proposal, July 2023 TC39 meeting updates:
  • Moved back to stage 3
  • Added /actual/ namespaces entries, unconditional forced replacement changed to feature detection
• Promise.withResolvers proposal, July 2023 TC39 meeting updates:
  • Moved to stage 3
  • Added /actual/ namespaces entries, unconditional forced replacement changed to feature detection
• Set methods stage 3 proposal, July 2023 TC39 meeting updates:
  • Throw on negative Set sizes, proposal-set-methods/88
  • Removed IsCallable check in GetKeysIterator, proposal-set-methods/101
• Iterator Helpers stage 3 proposal:
  • Avoid creating observable String wrapper objects, July 2023 TC39 meeting update, proposal-iterator-helpers/281
  • Iterator is not constructible from the active function object (works as an abstract class)
• Async explicit resource management:
  • Moved back into the initial proposal -> moved to stage 3, proposal-explicit-resource-management/154
  • Added /actual/ namespace entries, unconditional forced replacement changed to feature detection
  • Ignore return value of [@@​dispose]() method when hint is async-dispose, proposal-explicit-resource-management/180
  • Added ticks for empty resources, proposal-explicit-resource-management/163
• Added some methods from Float16Array stage 3 proposal:
  • There are some reason why I don't want to add Float16Array right now, however, make sense to add some methods from this proposal.
  • Methods:
    • Math.f16round
    • DataView.prototype.getFloat16
    • DataView.prototype.setFloat16
• Added DataView get / set Uint8Clamped methods stage 1 proposal:
  • Methods:
    • DataView.prototype.getUint8Clamped
    • DataView.prototype.setUint8Clamped
• Used strict mode in some missed cases, #​1269
• Fixed a Chromium 117 bug in value argument of URLSearchParams.prototype.{ has, delete }
• Fixed early WebKit ~ Safari 17.0 beta Set methods implementation by the actual spec
• Fixed incorrect Symbol.{ dispose, asyncDispose } descriptors from NodeJS 20.4 / transpilers helpers / userland code
• Fixed forced polyfilling of some iterator helpers that should return wrapped iterator in the pure version
• Fixed and exposed AsyncIteratorPrototype core-js/configurator option, #​1268
• Compat data improvements:
  • Sync Iterator helpers proposal features marked as supported from V8 ~ Chrome 117
  • Array grouping proposal features marked as supported from V8 ~ Chrome 117
  • Mark Symbol.{ dispose, asyncDispose } as supported from NodeJS 20.5.0 (as mentioned above, NodeJS 20.4.0 add it, but with incorrect descriptors)
  • Added Electron 27 compat data mapping

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @edx/react-unit-test-utils@1.7.0
npm ERR! Found: @edx/frontend-build@12.9.0-alpha.6
npm ERR! node_modules/@edx/frontend-build
npm ERR!   dev @edx/frontend-build@"12.9.0-alpha.6" from the root project
npm ERR!   peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/frontend-platform@4.6.1
npm ERR!   node_modules/@edx/frontend-platform
npm ERR!     @edx/frontend-platform@"4.6.1" from the root project
npm ERR!     peer @edx/frontend-platform@"^4.0.0 || ^5.0.0" from @edx/frontend-component-footer@12.2.1
npm ERR!     node_modules/@edx/frontend-component-footer
npm ERR!       @edx/frontend-component-footer@"12.2.1" from the root project
npm ERR!     1 more (@edx/frontend-component-header)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @edx/frontend-build@">=8.1.0" from @edx/react-unit-test-utils@1.7.0
npm ERR! node_modules/@edx/react-unit-test-utils
npm ERR!   @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @edx/frontend-build@12.9.10
npm ERR! node_modules/@edx/frontend-build
npm ERR!   peer @edx/frontend-build@">=8.1.0" from @edx/react-unit-test-utils@1.7.0
npm ERR!   node_modules/@edx/react-unit-test-utils
npm ERR!     @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/c9d95e/59cc2f/cache/others/npm/_logs/2023-09-04T07_12_51_722Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/c9d95e/59cc2f/cache/others/npm/_logs/2023-09-04T07_12_51_722Z-debug-0.log