CLI: Add eslint-plugin-storybook to automigrate

[yannbf]

Issue: N/A

What I did

This PR adds a new automigration step: eslint-plugin.

It will:
1 - Check if the user has eslint but does not have eslint-plugin-storybook
2 - If that is the case, it will check if the .eslintrc file of the user is supported (js or cjs)
3 - It will install the eslint-plugin-storybook dependency
4.1 - After that, if the eslintrc is supported, it will write the configuration in the eslint file.
4.2 If the eslintrc file is unsupported (json, yml, yaml), it will log a warning with instructions to install manually (but successfully install the dependency)

What this depends on

The eslint plugin is not ready, so this should not be merged until it is published.

How to test

• Is this testable with Jest or Chromatic screenshots?
• Does this need a new example in the kitchen sink apps?
• Does this need an update to the documentation?

1 - go to examples/official-storybook
2 - add eslint in package.json
3 - add a .eslintrc.js file in examples/official-storybook:

module.exports = {
  extends: ['plugin:prettier/recommended'],
  plugins: ["react", "@typescript-eslint"],
  rules: {
    'some/rule': 'warn'
  }
};

4 - run yarn build cli
5 - run ../../lib/cli/bin/index.js automigrate

[nx-cloud]

Nx Cloud Report

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

📂 See all runs for this branch

Status	Command
	nx run-many --target=prepare --all --parallel --max-parallel=15

---

Sent with 💌 from NxCloud.

[kylegach]

See my comment

[shilman]

Chef's kiss 😽

[yannbf]

@shilman I think this is good to go. I don't think this caused the failures in the E2E, have you seen these failures elsewhere?