Keep track of all reimported date ranges in case reimported ranges fall outside initial range

Nobody has claimed this yet.

If a user imports a range, then reimports dates outside of that range, there is a danger they may invalidate/re-archive those dates and lose GA data permanently.

The workflow for this bug would be:

- User imports, eg, 2020-07-01,2020-08-01
- User re-imports 2020-06-03,2020-06-04
- User later invalidates 2020-06-03 and re-archives
- This results in no data displaying for that day

This is due to GoogleAnalyticsImporter::isRequestAuthorizedToArchive() thinking, since the date is not within the main import date range, we can safely re-archive it.

To prevent we need to keep track of every re-imported date range as well the main one.

Note: this is an edge case.

Start by reading GoogleAnalyticsImporter::isRequestAuthorizedToArchive() and trace how the main import date range and reimported ranges are represented. Reproduce the workflow with an initial range followed by dates outside it, then verify that invalidating and re-archiving any date from a reimported range cannot incorrectly remove its Google Analytics data.

Written by the indexing model from the issue text.