Compare based on value and not identity

Using `is` in python will compare the two variables for identity i.e. if
they are the same reference to a thing. When you have small numbers
python has a optimization where it will use the same underlying object
and `is` will work. When you are using larger numbers they will no
longer be represented by the same underlying object so using `is` will
return false even if the objects represent the same underlying number.

For this reason it is always sensible to use `==` style comparison for
numbers.
Merge pull request #96 from alphagov/bugfix/value-not-identity

Compare based on value and not identity
Adds a webtrends collector for daily reports data

This does not handle the special case of keymetrics.

By default it collects daily. This means that for a given date range it
will make a query for every day in that range in an inclusive fashion
(e.g. the last day will be 'end_at' to 'end_at + 1' day). This is
because the api aggregates date ranges by default. Most of the logic is
doing this querying and parsing the date formats used by webtrends and
the nested json returned by the api.

The main integration type test is test_collect_parse_and_push.

This also includes some changes to data_parser to handle empty special
fields (though this is not needed in this collector).

The use of this new collector will be documented fully in the collector config
repo.
Handle when we already have a date from start at and end at
Handle no data in period for webtrends

e.g. when no visitors on a day
Handle when no data passed to push

this is possible from webtrends when there is no data in a period e.g.
for visitors
Remove timeSpan for data parser

this is specific to ga and should not be here