add UseLintFixmeCommentRule

[jimmylai]

Summary

add UseLintFixmeCommentRule to warn on deprecated noqa comment.
Converting a noqa to lint-fixme requires extra information (lint rule name) which makes it hard to provide autofix.
It also requires moving inline noqa comments to a standalone line.
We could consider provide a VSCode plugin as follow up that can suggest adding a lint-fixme or lint-ignore given a lint warning as a second option.

Test Plan

tox -e py38 -- fixit.tests.UseLintFixmeCommentRule

[Kronuz]

I guess you could use that regex instead, to handle when users use #noqa (no space, or multiple spaces) or when users put noqa after another comment. But for simplicity, I think handling uppercase/lowercase # noqa could be enough.

[jimmylai]

I guess you could use that regex instead, to handle when users use #noqa (no space, or multiple spaces) or when users put noqa after another comment. But for simplicity, I think handling uppercase/lowercase # noqa could be enough.

The regex requires one specific space before noqa. For the case of noqa after another comment, as long as the comment starts with noqa, it's a valid noqa comment which we want to show this warning.

Fixit/fixit/common/config.py

Line 34 in ef5edca

r"^# noqa(?!-file)(?:: (?P<codes>([a-zA-Z0-9]+,\s*)*[-_a-zA-Z0-9]+))?",