WRP-6904: Remove eslint-related modules

[hong6316]

Checklist

• I have read and understand the contribution guide
• A CHANGELOG entry is included
• At least one test case is included for this feature or bug fix
• Documentation was added or is not needed
• This is an API breaking change

Issue Resolved / Feature Added

Previously, there were attempts to install each eslint-related module in one repo(ex: eslint-config-enact) so that each tooling (dev-utils, cli, storybook-utils, ui-test-utils) does not install additional eslint-related modules.
The installation of eslint-config-enact alone did not install the necessary eslint-related modules, so it had to be managed separately, and the reason was not known.
This patch is a workaround for a longstanding eslint/eslint#3458 that would allow a shared ESLint config to bring along its own plugins, rather than imposing peer dependencies on every consumer of the config.
Doing so greatly reduces the copy+pasting and version management for all the other projects that use your standard lint rule set, but don't want to be bothered with the details.

References

• discussions: Support having plugins as dependencies in shareable config eslint/eslint#3458
• workaround: https://www.npmjs.com/package/@rushstack/eslint-patch

Resolution

Remove eslint-related modules and apply enactjs/eslint-config-enact#66

Additional Considerations

We can remove eslint-related modules after release enactjs/eslint-config-enact#66

Links

WRP-6904

Comments

Enact-DCO-1.0-Signed-off-by: Taeyoung Hong (taeyoung.hong@lge.com)

[sjro]

LGTM