Access to Memory (AtoM)

To reproduce:

1. Create a new archival description
2. Set the creation date to 0000-00-00
3. Save

Result:

The archival description will not be present under browse / search subsequently (as the ES indexing failed).

Subsequently trying a php symfony search:populate from the CLI, results in the error:

index: /atom_cca/QubitInformationObject/3165262 caused MapperParsingException[failed to parse [dates.endDate]]; nested: MapperParsingException[failed to parse date field [0000-12-], tried both date format [dateOptionalTime], and timestamp number with locale []]; nested: IllegalArgumentException[Invalid format: "0000-12-" is malformed at "-"]; 

Expected result:

Our ES indexing code shouldn't choke when given a year 0000 date.

Ideally, we'd have a validator on dates that the user enters from the UI that denies them the ability to enter a year of 0000, since that year doesn't exist. But now we know there are clients out in the wild with these dates already in their data, so we'll have to make our indexing code more robust against this bug regardless.

I'll create a separate ticket for adding better date validation.