If we append, "weboob.x" will not be resolved by regular Finders so our
custom finder will be hit. However, for importing "weboob.x.y", standard
Finders will find something, basing on "weboob.x.__spec__", and eventually
duplicating python modules, precisely what we wanted to avoid.
To ensure our custom Finder is called even for "weboob.x.y", prepend it.

Use case: the core does "import woob.x" but some app does "import
weboob.x". This loaded modules twice and prevented isinstance() from
cooperating. This trick loads modules only once.

In setuptools, it's not possible to have an optional dependency
triggering what files are installed and how to build certain files, we
have to make 2 setup.py.
Unfortunately, having 2 setup.py files does possible in one repository.
So, we have to split the repository in 2.
After this point, the repository will fork. One repository will take only
qt stuff, and the other repository will contain browser framework, cli apps
and modules.

Qt apps are under the weboob.applications package though.
To have 2 pip packages shipping files in the same root
package (weboob.*), the package must be namespaced. This can be achieved
by tweaking all ancestor __init__.py files.

I used autopep8 on some files and did carefully check the changes.
I ignored E501,E302,E231,E225,E222,E221,E241,E203 in my search, and at
least E501 on any autopep8 run.

Other style fixes not related to PEP8:
* Only use new-style classes. I don't think the usage of old-style
  classes was voluntary. Old-style classes are removed in Python 3.
* Convert an if/else to a one-liner in mediawiki, change docstring style
  change to a comment something that wasn't really appropriate for a
  docstring.
* Unneeded first if condition in meteofrance