chore(common): upgrade eslint

[eunjae-lee]

What?

This PR upgrades eslint to v9 which changes the configuration file very much. However, I'm not migrating the previous config exactly as-is. The previous rules are very custom, but I'm suggesting to go back to the recommended config sets by the official packages.

• It's community standard (it can go far until we actually need to tweak it for our own needs)
• As long as we keep this configs, the code is consistent everywhere.
• The root eslint config is applied to the whole repository whereas some packages used to have their own eslint config.
• No need to maintain many instances of eslint dependency and config within the repository.
• Only one exception here is that packages/cli/templates/react has its own eslint config, but it's actually almost the same as the root config. And we're not using that config in our repository. This config will be used when the CLI creates a new React project for users. Vue and Vanilla templates doesn't have eslint config baked in, because the official vite's templates for Vue and Vanilla doesn't include them. And we leave them empty so that people can adapt different linters & configs (https://eslint.style/ or https://biomejs.dev/)

Why?

JIRA: SHAPE-7107

How to test? (optional)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
plugin-sandbox	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 23, 2024 1:38pm

[eunjae-lee]

Sorry for the big PR 🙏🏻

[demetriusfeijoo]

Hey @eunjae-lee 🙌
massive job 💯

So nice to see most of the eslint comments removed and also to have just one config file to handle everything. 😍

I just noticed some eslint warnings that I guess you will address still

But overall, the PR looks solid so I'll approve it and then you can fix the warnings in your time 🙌

[eunjae-lee]

Hey @eunjae-lee 🙌 massive job 💯

So nice to see most of the eslint comments removed and also to have just one config file to handle everything. 😍

I just noticed some eslint warnings that I guess you will address still

But overall, the PR looks solid so I'll approve it and then you can fix the warnings in your time 🙌

Actually Vue 2 has a bad typescript support, and our vue 2 template is not even using typescript. So I believe we could ignore some warnings in the vue 2 template :)

But I will fix other issues if we encounter any in separate PRs. I will merge it for now, so that the other PRs aren't too affected much by this.