fix(storybook): add Emotion v11 support to current Nx Storybook setup

[juristr]

Current Behavior

Right now the Storybook + Emotion v11 is broken. There's more in this issue here:
storybookjs/storybook#13277

Expected Behavior

This PR detects whether Emotion v11 is being used and applies a patch to the Storybook webpack config to make sure Emotion v11 works seamlessly. Note, this only works if you use the @nrwl/react/storybook preset described in this doc. All
newly generated Nx v12.7+ workspace Storybook configurations will already use this out of the box.

Related Issue(s)

Fixes #

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/4yAKw5YuLdRJ344MPuKjTeVpgth4
✅ Preview: Canceled

[Deployment for f50cfc5 canceled]

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit f50cfc5. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx affected --target=e2e --base=3b2f0b64ea19d2c41c30b273ef25d71c5e4732e9
	nx affected --target=lint --base=3b2f0b64ea19d2c41c30b273ef25d71c5e4732e9 --parallel --max-parallel=4
	nx affected --target=test --base=3b2f0b64ea19d2c41c30b273ef25d71c5e4732e9 --parallel --max-parallel=2
	nx affected --target=build --base=3b2f0b64ea19d2c41c30b273ef25d71c5e4732e9 --parallel --max-parallel=3
	nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[puku0x]

This patch can be removed after Nx supports Storybook v6.4
storybookjs/storybook#16613

[puku0x]

Storybook v6.4 has been released. We can revert this fix and use emotionAlias flag for Emotion v11.

module.exports = {
  features: {
    emotionAlias: false,
  }
}

https://github.com/storybookjs/storybook/blob/80410528e8911ec4e1708899aec96ae8196d829e/MIGRATION.md#emotion11-quasi-compatibility

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.