Include config and logo url in instance API response

The mobile apps need access to the custom color and logo settings for
the instance so I have added them to the instance info API endpoint. I
decided to only include white listed config values in the response to
avoid possibly leaking sensitive config data to anyone with an API
key. We do not have any sensitive data now, but the config hash is a
dynamic grab bag and it is safer to not worry about what could be in
it.
Merge pull request #1182 from jwalgran/topic/api-branding

Include config and logo url in instance API response
Pin grunt since it doesn't work with our setup past version 4.1
Support javascript testing outside of a VM
Merge pull request #1190 from mtedeschi/topic/style-new-ui

Advanced search/add process styling
Merge branch 'new-ui'
Fix broken unit tests
Merge branch 'new-ui' into release
Fix typo trees -> resources and format visibility
Convert benefit_value_row to span instead of dl

So the benefit data appears on one line
Provide default resource basis for eco template

For some reason, template tags are not working correctly within the eco_benefits.html template. Non existent key values are not rendering with a 'default' filter. I thought that any failure would result in a comparitable falsy value, so you can say {{ dictionary.nonexistent_key|default:"empty" }}, but this appears not to work. It is unclear if {% with %} and {% blocktrans %} have anything to do with it.

To sidestep this issue, provide default values.
Merge pull request #1200 from steventlamb/bug/fix_ecobenefit_formatting

Bug/fix ecobenefit formatting
Fix unassigned instance in OTM1 audit migrations

model_hasattr was not returning a value for the success case where getattr doesn't raise.
Fix audit migrations

Update the object_id to the newly created OTM2 ids for all audits.

For 'create' audits, which are really 'pk' changes, update the 'pk' value to the correct OTM2 id.
Add mgmt command for basic otm1 migration checks
Remove empty values from clickedIdStream

fixes #1098 on github

clickedIdStream represents the id of other features clicked from the mapFeature page map, allowing you to jump to that other feature's page. However, all clicks to the map were producing values in the stream, even ones that were not tied to an actual feature.

This fixes #1098 on github because the clicking of another feature tries to jump to a different page, which is blocked/prompted by the statePrompter during edit mode.
Add backend and templates for advanced search display filters
Fix ecobenefits searches for queries containing string parameters
Add support for display filters to search.js

 - Switched to ids in buildElems, since all search elements have ids now
   - This does require slightly changing things, to avoid breaking MIN/MAX
 - Added more tests
Fixes #1192, Add labels to advanced search ranges