Remove old pylint rules from configuration

[folmos-at-orange]

Description

Our pylint ignore configuration has many obsolete rules that are not present anymore in pylint. These are rules mostly related to Python 2. If we remove them we'll simplify significantly the pyproject.toml file.

Questions/Ideas

• New List (found by program):

[tool.pylint.messages_control]
disable = [
  # Our exceptions
  "too-many-lines",
  "unnecessary-dunder-call",

  # Google pylint exceptions (https://google.github.io/styleguide/pyguide.html)
  "abstract-method",
  "arguments-differ",
  "attribute-defined-outside-init",
  "c-extension-no-member",
  "consider-using-enumerate",
  "duplicate-code",
  "fixme",
  "global-statement",
  "import-error",
  "import-self",
  "inconsistent-return-statements",
  "locally-disabled",
  "missing-function-docstring",
  "no-else-break",
  "no-else-continue",
  "no-else-raise",
  "no-else-return",
  "no-member",
  "no-name-in-module",
  "signature-differs",
  "suppressed-message",
  "too-few-public-methods",
  "too-many-ancestors",
  "too-many-arguments",
  "too-many-boolean-expressions",
  "too-many-branches",
  "too-many-instance-attributes",
  "too-many-locals",
  "too-many-nested-blocks",
  "too-many-public-methods",
  "too-many-return-statements",
  "too-many-statements",
  "trailing-newlines",
  "unnecessary-pass",
  "useless-else-on-loop",
  "useless-object-inheritance",
  "useless-suppression",
  "wrong-import-order",
]

• Obsolete messages (not present in the current pylint)

obsolete = [
"bad-continuation",
"bad-whitespace",
"apply-builtin",
"backtick",
"bad-option-value",
"basestring-builtin",
"buffer-builtin",
"cmp-builtin",
"cmp-method",
"coerce-builtin",
"coerce-method",
"delslice-method",
"div-method",
"eq-without-hash",
"execfile-builtin",
"file-builtin",
"filter-builtin-not-iterating",
"getslice-method",
"hex-method",
"idiv-method",
"implicit-str-concat-in-sequence",
"import-star-module-level",
"input-builtin",
"intern-builtin",
"invalid-str-codec",
"long-builtin",
"long-suffix",
"map-builtin-not-iterating",
"misplaced-comparison-constant",
"metaclass-assignment",
"next-method-called",
"next-method-defined",
"no-absolute-import",
"no-init",
"no-self-use",
"nonzero-method",
"oct-method",
"old-division",
"old-ne-operator",
"old-octal-literal",
"old-raise-syntax",
"parameter-unpacking",
"print-statement",
"raising-string",
"range-builtin-not-iterating",
"raw_input-builtin",
"rdiv-method",
"reduce-builtin",
"relative-import",
"reload-builtin",
"round-builtin",
"setslice-method",
"standarderror-builtin",
"sys-max-int",
"unichr-builtin",
"unicode-builtin",
"unpacking-in-except",
"using-cmp-argument",
"xrange-builtin",
"zip-builtin-not-iterating",
]

[popescu-v]

Very relevant to #347, so that we have as clean a package metadata specification as possible.

[popescu-v]

IMHO, this should be the reference: https://pylint.readthedocs.io/en/latest/user_guide/checkers/features.html.

[folmos-at-orange]

IMHO, this should be the reference: https://pylint.readthedocs.io/en/latest/user_guide/checkers/features.html.

Do you mean to use all the features indicated here? If that's the case it would be very "naggy", that's why we choose the google list as it is curated.