Fixed a few tests.
Added another test for "Access to roof for inspections"
Added a test for reporting/49/ because its 2nd graphs does not add up correctly.
be wary of nulls in json_extract

This can happen because the value is null, or is malformed, or doesn't
contain the specified property. We'll treat these all as not matching,
so that these broken values show up as 'Other', and the totals work
out right.
Merge branch '43-histograms' of github.com:solarpermit/solarpermit into 43-histograms
Merge branch '43-histograms' into devel
fix json_valid return type

don't want mysql to try to parse a string that isn't there...
Merge branch '64-reports-should-add-up' into devel
convert website tables to utf8

In MySQL we have to use utf8mb4 and utf8mb4_unicode_{ci,cs} in order
to support text outside the BMP.
remove collation from reporting queries

Now that all the tables have the correct character set and collation,
we don't have to specify it on every query.
you can now filter a report to a list of states/counties/jurisdictions

The way the query is built is somewhat dodgy, you need to specify the
exact county names or jurisdiction numbers, there's no ui at all and
I've made no provision for comparing the results from multiple filters
so the urls might change later. Other than that it's ok.

for #67
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
fixed some tests that had become broken and improved others