test ical data
New recurring test, and look for ical data in new place
Wipe all events between tests by default.

Unless the test says otherwise, wipe all events from the mock object before
starting each test.

That way, each test can easily compare the list of events to what it expects to
see, and not see stuff from previous tests there - but tests which want to build
upon previous results (e.g. testing that events no longer in the source iCal
feed get deleted, updated events get updated, etc) can do so.
Expectation for test1.data
Compare against summarised events representation.

Also dump some excess debug output.
update_google_calendar doesn't return success/fail