Update Storybook to work with Next 11

[kalvinwang]

Update Storybook to work with the recent changes in #390

All changes are the result of following the docs for 3.0 located at https://storybook.js.org/addons/storybook-addon-next-router, and removing 1.x/2.x-specific changes

I checked every component in Storybook sidebar to ensure that it's working

===

• Relevent Documentation (e.g. READMEs, Technical Foundation) updated
• Issue AC are copied to this PR & are met
• Changes are tested on Staging post-merge into main

[rocketnova]

The code in this PR looks good, but I've found another artifact from #390. After #390, yarn build is providing slightly different info.

Before:

$ next build
(node:45901) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at <snip>ui-claim-tracker/node_modules/next/node_modules/postcss/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
info  - Loaded env from <snip>/.env.local
info  - Using external babel configuration from <snip>/ui-claim-tracker/.babelrc
info  - Creating an optimized production build
info  - Compiled successfully
info  - Collecting page data
info  - Generating static pages (6/6)
info  - Finalizing page optimization
<snip>

After/Now:

$ next build
info  - Loaded env from <snip>/ui-claim-tracker/.env.local
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info  - Checking validity of types
warn  - The Next.js plugin was not detected in your ESLint configuration. See https://nextjs.org/docs/basic-features/eslint#migrating-existing-config
info  - Using external babel configuration from <snip>/ui-claim-tracker/.babelrc
info  - Creating an optimized production build
info  - Compiled successfully
info  - Collecting page data
info  - Generating static pages (6/6)
info  - Finalizing page optimization
<snip>

1. Is there a way to resolve the Next.js plugin warning?
2. Are we expecting to use webpack 5?

[kalvinwang]

1. Thanks for catching! Not that I can figure out quickly, but I've created a ticket. The warning is a little misleading, it's indicating that there's a new enhancement in Next 11 we haven't integrated yet, not that there's a regression.
2. Yup! It's part of the benefit of updating. Also we're still using webpack 4 for storybook.

[rocketnova]

Thanks for answering my questions. LGTM!