Cap the number of lint-amnesty comments

[kdmccormick]

People are constantly adding:

# lint-amnesty, pylint: disable=xyz

instead of just:

# pylint: disable=xyz

because they don't realize that lint-amnesty has a special meaning (that is: pylint violations which were grandfathered in because they were introduced before we enforced linting).

If we want lint-amnesty to continue to mean something, then we need to add a check that will hard-code a maximum number of lint-amnesty comments and fail CI if any more area added.

Alternatively, we call it a wash and blanket replace every occurance of lint-amnesty, pylint: with pylint:

[UsamaSadiq]

Since there is no immediate plan of fixing all pending lint-amnesty warnings, I believe second approach should be more beneficial i.e. changing lint-amnesty, pylint: to just pylint: . Also, it'll be a more straight forward task than introducing a new check.

[kdmccormick]

Agreed