Remove the need for a settings_local.py (bug 1050155)

fixes [bug 1050155](https://bugzilla.mozilla.org/show_bug.cgi?id=1050155)

This means that the `settings_local.py` won't be used automagically by `manage.py` anymore. If you want to use it, either:
- rename it to `local_settings.py` (imported, if it exists, by the new `settings.py` file), and make sure that you change the first line to be `from settings import *` (don't import from `lib/settings_base.py` or from `default.settings` directly, I'm not sure what would happen)
- use `DJANGO_SETTINGS_MODULE=settings_local` or the `--settings=settings_local` parameter when you run commands.

I've checked with @jasonthomas, this should be ok with his last changes (can you please give a look at this PR and confirm that it looks ok to you?)
What would the benefit be? Having a settings file which contains default for developers (straight out of a git clone) is what this PR is about.

Still having a separate, more "production oriented" `lib.settings_base` file seems useful, don't you think? Otherwise we'll have to duplicate most of the current `lib.settings_base` settings differences (from the `settings` file) to the `sites/` settings, incurring quite a lot of repetition.