Allow pinning of start and end dates in query.

We want to allow users to 'pin' the start and/or end date of a
query.

Add options in query.js to allow this.

Note that the start and end dates are only set if the 'period'
parameter is also set: this replicates the existing logic.

Update tests.
Allow grouped_timeseries to pin start/end dates.

Update module, collection, and collection test.
Allow completion modules to pin start/end dates.

Update modules, collection, and collection tests.
Use existing attributes on query change.

This is important for tabbed modules. It ensures that if a start or
end date is set by the initial query, we will continue to use it
on subsequent queries made by other tabs.

The only exception is the availability tabs, which switch period,
and where we therefore want to reset the start date according
to the period.

NB: All this will be superseded by the "tabbable modules" story,
due to be checked in shortly. It is an interim fix.
Allow availability modules to pin end dates.

Update modules, collection, and collection tests.

Don't pin start dates since it's hard to think of a scenario where
this would make sense for this module.
Archive the deposit-foreign-marriage page.

Pin end dates at 30 December 2013.

Update dashboard description to explain that the transaction no longer
exists.

Remove realtime module (since it doesn't make sense to show this) and
journey module (as agreed with Matt).

Remove link to this dashboard from Performance home page.

Pivotal story: https://www.pivotaltracker.com/s/projects/911874/stories/63389134
Show all available data on G-Cloud dashboard.

G-Cloud has data from April 2012 onwards, and the original designs included
all this data.

Pin start date to April 2012 in order to show all available data.
Include data from clock change on no-realistic-dashboard.

The 24-hour availability view now covers the switch from
BST to GMT, so we can easily see if there are any problems.

I've also pinned one of the completion graphs to an end date,
since it seemed like a good idea to include another example
of this on no-realistic-dashboard.
Fix bug in live-service-usage graph rendering.

We were checking for the existence of the collection before
rendering the template HTML for live-service-usage graphs.

Unfortunately, this got us into an occasional race condition
between templateContext and initialize, so sometimes the
graphs weren't rendering.

The template check isn't really useful anyway, because we
don't have error handling in the collection yet, so the
graphs will probably break before this point if there is
no data in the collection.

So: remove this check from the template, and remove
templateContext from the view.
Remove unnecessary test
Upgrade the frontend toolkit

This includes a change that removes Ruby specific syntax from the
toolkit.

https://github.com/alphagov/govuk_frontend_toolkit/commit/7b0e4ce8b35434238d1df1596f3ef60aff7d526e
Switch from Ruby Sass compilation to Node Sass

It's *much* quicker now. User time:

              Ruby                     Node.js (libsass)
Development   1.199s 0.871s 0.908s     0.486s 0.539s 0.490s
Production    3.627s 3.329s 3.271s     0.581s 0.475s 0.552s
Enable Sass source maps

In development when using a supported browser like Chrome, the inspector
will now show you the Sass file that the CSS originated from rather than
the compiled location.
Only render periods if we actually have some previous period data.

This is useful for rendering single stat type values through a kpi template.
Merge pull request #320 from alphagov/switch-from-ruby-to-node-sass

Switch from Ruby to Node.js Sass
Fix print styles.

Pivotal story:
https://www.pivotaltracker.com/s/projects/911874/stories/66047406

Setting media='all' rather than media='screen' carries our graph
styles through to the print stylesheet.

Also update tests.
Merge pull request #323 from alphagov/bugfix/fix-print-styles

Fix print styles.
Add graph of waste carriers registration over time

I believe this is the most we can do with the data in its current format.

https://www.pivotaltracker.com/story/show/63891934
Merge pull request #324 from alphagov/waste-carriers-graphs-registrations-time

Add graph of waste carriers registration over time
Added waste carrier total registration using the kpi module