frontend.shared.resource_lib: Ignore false negatives from pylint

Here entry_class is callable by the time it is used, due
to some hackery that is probably too hard to fix right
now. So make pylint ignore the error, so we have more
useful pylint reports.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
run_pylint: Ignore error I0011 on quiet runs

For quiet runs, telling that we're ignoring some false
negatives is not really necessary.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
base_job: Ignore pylint warning

In this particular case, the unittest overrides the
mentioned functions with the purpose of mocking it,
so it's OK it is there. Therefore, taking another
step for a clean pylint quiet run, silence those
errors by appending the appropriate comments.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
tko/nightly.py: Remove irrelevant file

This file was added upstream by mistake, and it was
never supposed to work because it lacked one library
that was yet another database wrapper. Let's just
get rid of it.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
pylint: Disable some E0611 false positives

Autotest uses a site extension mechanism that allows
for extending the functions/API of the framework. But
in upstream code, such extensions won't be there,
reason why it is OK to ignore if they are missing.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
client.shared.test_utils.unittest: Clear E0213 false positive

_deprecate here is used with the very specific purpose
of decorating the unittest comparison methods that are
deprecated so unittest writers don't use them.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>