[pylint] Do not report methods with only one EM101-compatible raise (PLR6301)

[InSyncWithFoo]

Summary

Related to this comment by @DaniBodor at #12172. Tests adapted from that of #13714.

Test Plan

cargo nextest run and cargo insta test.

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[MichaReiser]

Thanks for working on this change but I'm not convinced this goes into the right direction.

Taking the exmaples from your tests. The self parameter is unused and unnecessary because Foo doesn't extend any base class. That's why I think this is in the spirit of PLR6301 to flag the self usage. I can see how the warning is annoying when prototyping an API but I'd simply ignore the warning in that case (either using a noqa or literally ignoring the warning).

The other case is where Foo extends from a base class but our recommendation there is to mark the method as @override.

That's why I think we should leave the rule as is but I'm interested in your perspective.

[InSyncWithFoo]

I still advocate for this change, as it improves consistency. Currently this triggers PLR6301 but not ARG002:

class Foo:
    # PLR6301: Method `lorem` could be a function, class method, or static method
    def lorem(self, v):
        msg = 'Lorem ipsum dolor sit amet'
        raise NotImplementedError(msg)

This triggers both:

class Foo:
    # PLR6301: Method `lorem` could be a function, class method, or static method
    def lorem(self, v):  # Unused method argument: `v`
        print(1 + 2)