[DDW-1149] Update part of vulnerable packages

[przemyslaw-wlodek]

This PR updates some of the packages that contain critical and high-severity vulnerabilities. Here is the list of the packages that did not get updated and can be treated as separate task:

Development deps, should not be impacting build (considered lower priority):

• dns-packet used by webpack-dev-server
• ua-parser-js used by storybook
• decode-uri-component used by @testing-library source maps, etc.
• glob-parent used by gulp, eslint and storybook

High risk and high/unknown upgrade effort:

• http-cache-semantics used by electron
• json5 used by many packages e.g. svg-inline-loader, storybook, eslint-plugin-import (svg-inline-loader is no longer maintained)
• d3-color used by recharts
• terser used by @storybook and webpack (we already have the latest version of webpack)

Testing Checklist

• Slack QA thread
• Test

---

Review Checklist

Basics

• PR assigned to the PR author(s)
• input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
• If there are UI changes, Alexander Rukin assigned as an additional reviewer
• All visual regression testing has been reviewed (assign run Chromatic label to PR to trigger the run)
• PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
• PR link is added to a Jira ticket, ticket moved to In Review
• PR is updated to the most recent version of the target branch (and there are no conflicts)
• PR has a good description that summarizes all changes
• PR contains screenshots (in case of UI changes)
• CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
• There are no missing translations (running yarn manage:translations produces no changes)
• Text changes are proofread and approved (Jane Wild / Amy Reeve)
• Japanese text changes are proofread and approved (Junko Oda)
• Storybook works and no stories are broken (yarn storybook)
• In case of dependency changes yarn.lock file is updated

Code Quality

• Important parts of the code are properly commented and documented
• Code is properly typed with typescript types
• React components are split-up enough to avoid unnecessary re-renderings
• Any code that only works in main process is neatly separated from components

Testing

• New feature/change is covered by acceptance tests
• New feature/change is manually tested and approved by QA team
• All existing acceptance tests are still up-to-date
• New feature/change is covered by Daedalus Testing scenario
• All existing Daedalus Testing scenarios are still up-to-date

After Review

• Update Slack QA thread by marking it with a green checkmark