moving loading of local.env to manage.py

[dave-leblanc]

So here's what was happening. New Django project from latest edge.

when deploying to the server because manage.py was looking for an ENV var to define the settings location without ever loading the local.env it was always looking for the development settings because that's what was defaulted in manage.py

subsequently this applied to wsgi.py which was defaulting to production. If a users local.env ever called for a different settings file it would not be loaded.

Moving the loading of the local.env file into the environment at the manage.py and wsgi.py levels means that it is no longer needed in settings.base

[dave-leblanc]

I've added an additional change to the gitignore as the /site/ dir being created inside project_dir was showing as an untracked change on my deployment server.