Revert all collection/module specific flatten=true

We want to move the application of flatten=true into a central location
so we need to remove all custom additions of flatten=true
Switch on flatten for everything

We were down to the last module as part of the switch over to flat
group_by data, so I migrated the addition of the flatten=true query
parameter from each individual module/collection into the data source.

This should make pulling it a little easier and ensures that all
requests will have this parameter provided (as everything uses
data_source).

This maintains the ability of a particular module to override this query
parameter as it as the json from stagecraft and any custom query
parameters get merged over the top.

I've hidden this behind a flag that is passed through to DataSource from
any instance of Collection. This has been done so that we don't have to
immediately move all of the test fixtures to representing flatten data
rather than the nested data. This will be done but decoupled from
enabling flatten for all.

I've had to switch completion to ask for whether it is flatten on demand
as it was trying to set up its own datasource and store the property.
Not sure why it was doing that.
Merge pull request #858 from alphagov/feature/flatten-everything

Feature/flatten everything
Fix "Very dissatisfied" label on user satisfaction module
Merge pull request #859 from alphagov/user-satisfaction-label-fix

Fix label on user satisfaction module
Merge pull request #860 from alphagov/bugfix/applications

No data view for applications module
Shim: set `flattenEverything` to `false` for grouped_timeseries

- Fixes our bug with huge unflattened timeseries data coming back
- Is a suitably horrible looking shim
Merge pull request #861 from alphagov/feature/unflatten-grouped-timeseries

Shim: set `flattenEverything` to `false` for grouped_timeseries
Use dashboard generator to update dashboards

The dashboard generator was originally written to take dashboards
from a Google Spreadsheet and save them as JSON files.

We now need to pull in changes from the Google Spreadsheet and
update the data stored in Stagecraft.

This commit retrieves the database ID for a given dashboard slug
and uses that to ensure the dashboard is overwritten in the
database rather than being duplicated.
Merge pull request #862 from alphagov/update-dashboard-generator

Use dashboard generator to update dashboards
Change the default dev config to use production

Cheapseats (our testing app) uses production by default, but until
this commit Spotlight was using preview. This causes test failures
because the instance of Spotlight that Cheapseats spins up is using
preview data, but it's making assertions against production
Stagecraft.
Merge pull request #863 from alphagov/default-dev-config-production

Change the default dev config to use production
Updated cheapseats to the latest version
Merge pull request #864 from alphagov/bugfix/update-cheapseats

Updated cheapseats to the latest version
Pass in required params to Trans Expl generator

The generated JSON needs to contain several fields on the module
that aren't currently present, including options, order, description
and type_id.

Also fix a bug where I was testing `response` rather than `res`.
Merge pull request #865 from alphagov/bugfix-transactions-explorer-generator

Pass in required params to Trans Expl generator
Use SPDY to connect to backing services

Spotlight currently makes a lot of backing service requests over SSL. We
should see an improvement in our response times by using SPDY to connect
to each domain/port combination over SPDY, and only pay the overhead of
setting up a single TCP connection to have a conversation over TLS.

Currently, a request to render HTML might make 10 requests. Default node
settings will allow up to 5 connections to be made to a host / port
combination, so we will have the overhead of setting up 5 TLS
connections, then hopefully see connection keep alive giving a slight
benefit.

This change needs benchmarking and profiling to ensure that we’re
using SPDY correctly.

Can be traced in wireshark / tcpdump with ip.addr == 37.26.89.53 on
preview.
Add clarification to 'report a problem' form

This text is intended to try and reduce the number of tickets that
we receive which should actually be sent to the product teams rather
than to us.

Clarify that the form on this page is for dashboard problems only.
Merge pull request #866 from alphagov/report-a-problem-clarification

Add clarification to 'report a problem' form
Merge pull request #867 from alphagov/feature/spdy

Use SPDY to connect to backing services