Migrate to Storybook 7 + fix vulnerabilities

[vbartonicek]

Before:

What I did:

1. npm audit fix to fix some of the vulnerabilities
2. npx storybook@next upgrade --prerelease to automatically upgrade Storybook to 7.0.0-beta.13
3. Rewrote custom story sort within .storybook/preview.jsx as described in https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#v7-style-story-sort
4. npm install --save-dev webpack to tackle following issue - Storybook build fails with "Cannot find module 'webpack/lib/util/makeSerializable.js" after upgrading storybook packages to 6.3.0 storybookjs/storybook#15336
5. npm audit fix - this run couldn't fix glob-parent <5.1.2 vulnerability
6. Deleted node-modules & package-lock.json and ran npm install to get rid of glob-parent <5.1.2 vulnerability

📚 Resources:
Storybook 7.0 beta - https://storybook.js.org/blog/7-0-beta/
Storybook 7 migration guide - https://chromatic-ui.notion.site/Storybook-7-migration-guide-dbf41fa347304eb2a5e9c69b34503937

After:

[linear]

PSL-1380 Update NPM dependencies and fix vulnerabilities

I just cloned the repo and running npm install reported 22 vulnerabilities.

Business Outcome:

As an Engineer I want to make sure our dependencies are up-to-date so that our repo's security&stability is increased.

Definition of done:

• Update NPM dependencies to latest version
• Fix all vulnerabilities

Additional Notes:

Some packages are deprecated and need a major update, e.g.

• fsevents@1 => 2
• chokidar@2.1.8 => 3

Screenshot

Screen Shot 2022-11-15 at 9.37.05 AM.png

[vbartonicek]

I'm bit confused by GitHub check failing on error TS2322: Type 'ConstructorIO' is not assignable to type 'CioClient' which seems to be unrelated to my changes 🤔

[deomsj]

🔥 🔥 🔥 Feels so good to have a clean terminal after npm ci

FYI: pushed a few commits to get our type definitions in this repo to play nice with updated type definitions in cio-client-js repo :)