These should be caught by our tests or `tox -e check` runs, which
currently don't use pylint. Since pylint is only run via code quality
checking platforms, it's ran in as without installing the package under
test so getting import errors is normal.

For some reason Codacy still mentions issues found via Prospector's
pylint integration, even though I disabled it in Codacy's settings.
That's why I'm trying to disable the errors directly in Prospector's
configuration file. Let's see whether Codacy picks this up.
Another option would be to disable running pylint through Prospector
completely by using ".prospector.yaml". I should try this, should the
configuration in this commit not work.

Apparently they are unnecessary because pylint also picks up the option
without them present.

The message codes where missing a leading "D".

According to Codacy's documentation, '.prospector.yaml' is legal, but
since it also displays a notification that it doesn't find a
configuration file for Prospector, I'm trying other variants. Using
".yml" as the extension is the first.

Since the bitshift operators are usually side effect free, using them
outside of an assignment or something similar looks like a statement
without an effect to a static code checker. Using `chain` might remedy
this.