chore(deps): update dependency rollup to v2.75.7

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rollup (source)	2.75.6 -> 2.75.7

---

Release Notes

rollup/rollup

### [`v2.75.7`](https://togithub.com/rollup/rollup/blob/HEAD/CHANGELOG.md#​2757) [Compare Source](https://togithub.com/rollup/rollup/compare/v2.75.6...v2.75.7) *2022-06-20* ##### Bug Fixes - Mark Array.prototype.group/groupToMap as side effect free. ([#​4531](https://togithub.com/rollup/rollup/issues/4531)) ##### Pull Requests - [#​4523](https://togithub.com/rollup/rollup/pull/4523): chore: remove source map workaround, bump deps ([@​dnalborczyk](https://togithub.com/dnalborczyk)) - [#​4525](https://togithub.com/rollup/rollup/pull/4525): Add regression tests for instanceof ([@​lukastaegert](https://togithub.com/lukastaegert)) - [#​4528](https://togithub.com/rollup/rollup/pull/4528): chore: Set permissions for GitHub actions ([@​naveensrinivasan](https://togithub.com/naveensrinivasan)) - [#​4531](https://togithub.com/rollup/rollup/pull/4531): fix: rename Array.prototype.group/groupToMap ([@​dnalborczyk](https://togithub.com/dnalborczyk)) - [#​4535](https://togithub.com/rollup/rollup/pull/4535): chore: bump resolve from 1.22.0 to 1.22.1 ([@​pos777](https://togithub.com/pos777))

---

Configuration

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

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• [ ] If you want to rebase/retry this PR, click this checkbox.

---

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

[renovate[bot]]

⚠ 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

real    0m7.983s
user    0m6.937s
sys 0m0.834s
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-image@4.0.3
npm ERR! Found: @testing-library/react@12.1.5
npm ERR! node_modules/@testing-library/react
npm ERR!   dev @testing-library/react@"13.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @testing-library/react@"13.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@18.2.0
npm ERR! node_modules/react
npm ERR!   peer react@"^18.0.0" from @testing-library/react@13.3.0
npm ERR!   node_modules/@testing-library/react
npm ERR!     dev @testing-library/react@"13.3.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! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-06-20T13_16_20_481Z-debug-0.log