[CCI] Update dependencies

[andreymyssak]

Description

Reopening #609.

Upgrading dependencies that do not cause breaking changes and do not make changes to the code.

Discovery/analysis can be found here #594 (comment).

Issues Resolved

#594

Check List

• New functionality includes testing.
• New functionality has been documented.
• All tests pass
  • yarn lint
  • yarn test-unit
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[ashwin-pc]

@andreymyssak sorry we got to this so late. Do you mind updating this PR to resolve the conflicts?

[BSFishy]

Passes all tests (apart from a11y, which is fixed in another PR), succeeds in both builds (yarn build and yarn build-docs)

[andreymyssak]

@ashwin-pc I'll update it soon, thanks for mentioning that.

[andreymyssak]

@BSFishy Can you run test-a11y on your side and see if it exits correctly? I've seen some issues where browser.close() didn't work correctly because there are open tabs that were not closed. If the issue is confirmed, I will roll back to a previous version and create a new PR, where this problem will be solved as follows:

const pages = await browser.pages();
for (let i = 0; i < pages.length; i++) {
  await pages[i].close();
}
await browser.close();

[BSFishy]

Tests fail, of course, because #640 hasn't been merged yet. However, beyond that it looks like everything exits properly. However, if there is an issue related to a specific platform (i.e. if this fix is needed for M1/M2 Macs), we should definitely get it in somewhere

[andreymyssak]

For reviewers, although the upgrade was to a major version, the current functionality of
compile-icons is not affected

[joshuarrrr]

Some package.json conflict resolutions needed, then we can merge.