Disallow to ignore some violations on line level

[sobolevn]

Rule request

Thesis

Sometimes developers inline ignore violations that should not be ignored. Like complexity violations, best practices, or any others that are important for this specific project.

So, we need to give users an option to provide a configuration hook with violations names (both short like WPS and full ones like WPS102) that cannot be ignored.

And when we find inline ignore of this violations - we should raise a new one on 0 line.

We do not check per-file-ignores and ignored with this check.

Related: https://github.com/wemake-services/wemake-python-styleguide/pull/1246/files#diff-2c42a0740c36d757ff4d489010b3138eR4

This is a best practices violation.

[edytagarbarz]

Hi, let me work on this!

[sobolevn]

@edytagarbarz you are welcome!

[webknjaz]

I have a case where I'm temporarily patching some other project and have a copy-pasted function that I edit (until the upstream releases a fix).
That function causes WPS231 Found too high function cognitive complexity: 13 > 12 and I don't really want to rewrite it keeping it as close to the original as possible.

What is the advice here if I cannot ignore this inline?

[sobolevn]

I am using quite similar idea in #1276
I just ignore patches/ folder for any complexity violation there is.