Remove no-confusing-arrow because of the deprecation of formatting …

…rules (#276)

First, this rule was deprecated in ESLint v8.53.0.
The alternative is the third-party plugin `@stylistic/eslint-plugin-js`.

Second, I sometimes feel annoying on this rule. For example, see:

```js
const result = () => (type === 'foo' ? foo() : bar());
/*             ^^ Arrow function used ambiguously with a conditional expression [no-confusing-arrow] */
```

In this case, I think it's enough readable, thanks to `()` around the function body.
So, I think this rule is no longer necessary in this shared config.

Ref:
- https://eslint.org/docs/latest/rules/no-confusing-arrow
- https://eslint.org/blog/2023/10/deprecating-formatting-rules
- https://eslint.style/packages/js

CHANGELOG.md

@@ -2,6 +2,7 @@
 
 ## Head
 
+- Removed: `no-confusing-arrow` because of the deprecation of formatting rules.
 - Changed: replace deprecated `padding-line-between-statements` with `@stylistic/js/padding-line-between-statements`.
 - Changed: bump `eslint-plugin-jest` from v27 to v28.
 - Changed: bump `eslint-plugin-n` from v16 to v17.

index.js

@@ -24,12 +24,6 @@ module.exports = {
 		'func-name-matching': 'error',
 		'func-names': ['error', 'as-needed'],
 		'guard-for-in': 'error',
-		'no-confusing-arrow': [
-			'error',
-			{
-				allowParens: false,
-			},
-		],
 		'no-console': [
 			'error',
 			{