Farewell, shifty hacker dude! May your 0days be many and your
indictments be few

Some differences are eventually likely to become permanent, because the
existing behaviour is unforgiveable.

Still needs a ton of work to emulate argument handling, shell selection,
and output emulation in every case. Unsurprisingly, Ansible documents
none of this.

Sending just via .call_async() would previously crash the child, now it
generates CallError like intended.

Python 2.4 does not support explicit relative imports. They were added
at Python 2.5, along with `from __future__ import absolute_import`.

On 2.x this will mean the import is first (implicitly) tried relative,
but on 3.x it will always be tried absolute.

Fixes #92

Hopefully these are correct, and clearerabout the
behaviour/pre-conditions of these methods.

Not sure how they got there, but Django doesn't use Jinja without
explicit configuration.

This matches a tweak made in 8765f761c995c31c9bff6287d881f0e9b5d0cfc5

There is only so much trackpad-driven yEd work one man can handle

I took the liberty of renaming ModuleFinder.STDLIB_DIRS to
_STDLIB_PATHS, since it felt like an implementation detail that
shouldn't be baked into a public API and stdlib can also be imported
from e.g. a zip file.

I also changed it to a set to handle any duplicates.

Fixes #86

The solution was that Mitogen's loader should emulate the behaviour of
ansible.executor.module_common, which restricts dependency scanning to
the ansible.module_utils namespace.