build: update dependency kagekiri to v2

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
kagekiri	devDependencies	major	^1.4.1 -> ^2.0.0

---

Release Notes

salesforce/kagekiri (kagekiri)

v2.0.0

Compare Source

Breaking changes

IE11 and other legacy browsers are no longer supported. Please only run kagekiri on the latest version of Chrome/Edge/Firefox/Safari, or use your own toolchain (e.g. Babel) to downlevel it to be compatible with IE11.

What's Changed

• chore: remove bundlesize, use custom script by @​nolanlawson in https://github.com/salesforce/kagekiri/pull/104
• chore: update rollup-plugin-istanbul by @​nolanlawson in https://github.com/salesforce/kagekiri/pull/105
• build(deps-dev): bump braces from 3.0.2 to 3.0.3 by @​dependabot in https://github.com/salesforce/kagekiri/pull/106
• build(deps-dev): bump body-parser from 1.19.2 to 1.20.3 by @​dependabot in https://github.com/salesforce/kagekiri/pull/108
• build(deps): bump ws, engine.io and socket.io-adapter by @​dependabot in https://github.com/salesforce/kagekiri/pull/109
• fix: drop support for IE11 and legacy browsers by @​nolanlawson in https://github.com/salesforce/kagekiri/pull/102
• fix: update dependencies by @​nolanlawson in https://github.com/salesforce/kagekiri/pull/111

Full Changelog: salesforce/kagekiri@v1.4.3...v2.0.0

---

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

---

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

---

This PR has been generated by Renovate Bot.

[devversion]

The changes were merged into the following branches: main, 20.0.x

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}