[eslint-config] Move from `@shopify/eslint-plugin` to `@antfu/eslint-config`

[NiccoloOlivieriAchille]

Use the @antfu/eslint-config library as the base for all the configurations:

base

import antfu from '@antfu/eslint-config';

export default antfu({
  stylistic: {
    semi: true,
    overrides: {
      'style/brace-style': ['error', '1tbs'],
      'no-console': 'off',
    },
  },
  typescript: {
    tsconfigPath: 'tsconfig.json',
  },
});

Then dunno if for cdk we can implement something similar to what is already implemented with shopify.
Keep in mind that shopify uses the old eslint config, while antfu uses the new one

[amazon-q-developer]

Progress Updates

• I'll help you implement the requested changes to move from @shopify/eslint-plugin to @antfu/eslint-config. First, I'll explore the repository structure to understand the current setup.
• Let's first look at the package.json to understand the dependencies and structure of the project.
• Now let's look at the current ESLint configuration:
• Let's examine the eslint-plugin package since that's what we need to replace:
• Let's look at the package.json for the eslint-plugin:
• Now let's look at the source code of the eslint-plugin:
• Let's also check if there are any tests for the eslint-plugin:
• Let's also check if there's a CLI component:
• Now that I understand the current setup, I'll create a new implementation using @antfu/eslint-config. I'll start by updating the package.json to include the new dependency.
• Now I'll update the main index.ts file to use @antfu/eslint-config instead of @shopify/eslint-plugin. I'll implement the bePowerFactory function to create configurations based on the provided options.
• Now I'll update the CLI config initialization file to use the new configuration format.
• Now I'll update the main eslint.config.js file in the root directory to use the new configuration.
• Now I need to update the tests to match the new implementation. The test counts will need to be adjusted since @antfu/eslint-config might generate a different number of rule sets.
• Analyzing test updates needed
• Let's update the tests to be more resilient:
• Let's update the README.md file to reflect the changes and provide information about the new configuration.
• Now let's update the README.md:
• Let's also update the main README.md to reflect the changes.
• Let's update the main README.md to mention the change to @antfu/eslint-config:
• Let's update the CHANGELOG.md to document the changes we've made.
• Let's update the CHANGELOG.md to add our changes:
• Let's try again with a smaller change:
• All the necessary changes have been implemented. Let's summarize what we've done.
• Summarizing the changes made

---

✅ I finished the proposed code changes, and the pull request is ready for review: #8.

Comment on the pull request to provide feedback and request a new iteration.

To provide feedback on how Amazon Q Developer performed with code generation, create an issue in the Amazon Q Developer public repository.