refactor!: migrate from eslint-plugin-react to eslint-react

[liby]

Description

Solve #156

[Rule Migration] migrate eslint-plugin-react rules.

[liby]

@eslint-react/no-useless-fragment always allow expressions.

[frantic1048]

This rule is already included in the plugin:@eslint-react/recommended-legacy preset. May we omit it?

https://github.com/Rel1cx/eslint-react/blob/3e3af56a1df933180e423a777887e66f72d2fcf0/packages/plugins/eslint-plugin/src/index.ts#L108

[frantic1048]

@eslint-react/naming-convention/filename-extension already defaults to "extensions": [".jsx", ".tsx"]. May we omit it?

In contrast, react/jsx-filename-extension defaults to "extensions": [".jsx"], thus we are manually set extensions in the past.

References:

1. @eslint-react/naming-convention/filename-extension: https://eslint-react.xyz/rules/naming-convention-filename-extension
2. react/jsx-filename-extension: https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-filename-extension.md
3. react/jsx-filename-extension issue about .tsx extension: Default values for the React /jsx-filename-extension rule  jsx-eslint/eslint-plugin-react#2919

[liby]

Okay, I will remove them. Previously, what I considered was to explicitly declare the rule configuration to avoid being affected by upstream changes.
However, we have corresponding config-snapshot.test.ts, so even if the default configuration upstream changes, we can still observe it here.