chore: upgrade to eslint v9 and migrate to flatconfig

[aliesenli]

Description of changes:

This PR upgrades ESLint to version 9 and migrates to the new flat-config format, which has been the default configuration format since ESLint v9.0.0.

The .eslintrc.json file has been removed in favor of the new eslint.config.js file.

Following packages has been adjusted to make this migration possible:

"@typescript-eslint/parser": "^8.13.0",  --> added parser to recognize react (built in)

"eslint": "^8.7.0",                      --> upgrade to "^9.14.0",
"eslint-config-react-app": "^7.0.1",     --> swapped with "eslint-plugin-react": "^7.37.2",
"eslint-plugin-mocha": "^10.2.0",        --> upgrade to "^10.5.0",

Patched the globals@11 to make linter happy
patches/globals+11.12.0.patch

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[aws-amplify-us-west-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1386.d16eby4ekpss5y.amplifyapp.com

[jorenbroekema]

Thanks for the PR, I migrated a bunch of repos to ESLint v9 recently and contemplated doing it for Style Dictionary but couldn't find the time for it, so this is much appreciated.

Just 1 suggestion for patching globals@11 version

[aliesenli]

Thanks for the PR, I migrated a bunch of repos to ESLint v9 recently and contemplated doing it for Style Dictionary but couldn't find the time for it, so this is much appreciated.

Just 1 suggestion for patching globals@11 version

Thanks for the suggestion! I've just patched the globals@11 and rebased onto main.

I think the package-lock(v4.1.4) and package.json(v4.2.0) are out of sync tho @jorenbroekema

[jorenbroekema]

I think the package-lock version gets out of sync quite a bit because during the version bump the package-lock would have to be synced by doing an npm install after the bump in package.json and committing that with the version bump, I guess our release orchestration (changesets) isn't doing this. It's not a problem imo but could be solved by doing npm install after rebasing on latest main and committing the pkg lock version bump. Not a blocker for me though

EDIT: #1387 fixed here for in the future.