use django-jinja to integrate with the Jinja2 templating engine

This only effects templates that are rendered via the proper django
apis, such as django.template.loader or django.shortcuts.render. Most
of our code is still going through
website.utils.httpUtil.HttpRequestProcessor in order to use Jinja2.

Additionally, django-jinja only uses the Jinja2 template engine for
template files that end in '.jinja'; it uses the Django template
engine for template files ending in '.html'. This means that the
built-in class-based generic views will work correctly, but will only
use Jinja2 if you give them a different template_name.
form for creating/editing a geographic area

includes a new dependency which implements the autocomplete form
fields.
rename migration; it conflicts with the one on branch 57-unicode-migration
jurisdiction type selection in geographic area creation form works
custom save method on the form to save the jurisdiction list
can now use geographic areas to limit the scope of a report
broke the line endings somehow; clean them up
make the filter detail page at least somewhat readable