Overlapping ESLint rules for unnecessary catch

[Tlacenka]

User story

As an engineer, I want only one ESLint rule to target a given issue, so that I only get one finding per issue and avoid unnecessary noise.

Acceptance criteria

There is only one rule for reporting unnecessary catch clauses.

Minimal reproduction of current behaviour

The vanilla no-useless-catch included from recommended config here.
The sonarjs/no-useless-catch included here does the exact same thing.

Desired behaviour showcase

The sonarjs/no-useless-catch rule can be removed,

Which configuration is this related to?

default

ESLint version

No response