Yaml Changes

When setting up furious for deployment in an appspot, I made a few changes. I changed the include-python27.yaml to just include.yaml and I added the handler for django-based projects. I also included a django.yaml for use in a django-enabled project instead of the default include.

The reason for the change in the name of the yaml is to allow the main app.yaml to use just:
- externals/py/furious 
in the includes: section. If left unspecified, the include statement will look for an include.yaml, so I figured it would be better to have that in the library.

The second change is simply to get the furious stuff to work in a complicated applications's context with all of the possible django pathing.