Do we want to remove `no-unused-disable` rule in our next major release?

We currently have a bunch of issues/PRs about the `no-unused-disable` rule: - #130 - #133 - #234 - #244 - #249 - #296 Looking at these, it seems like the rule isn't working on flat configs + it's also possible to get the same functionality either through the [`--report-unused-disable-directives`](https://eslint.org/docs/v8.x/use/command-line-interface#--report-unused-disable-directives) & [`--report-unused-disable-directives-severity`](https://eslint.org/docs/v8.x/use/command-line-interface#--report-unused-disable-directives-severity) (available as of [ESLint v8.56.0](https://eslint.org/blog/2023/12/eslint-v8.56.0-released)) CLI options or with the `linterOptions.reportUnusedDisableDirectives` configuration option (available as of [ESLint v8.56.0](https://eslint.org/blog/2023/12/eslint-v8.56.0-released)), which is enabled by default in ESLint v9. That's why I think we should remove `no-unused-disable` in our next major release. We can make it deprecated in a minor release though for smoother transitioning. CC/ @eslint-community/core-team @eslint-community/eslint-plugin-eslint-comments CC/ @CruseCtrl @cylewaitforit @DetachHead @FloBam @SamuelT-Beslogic @teppeis @Zamiell