Fix promise future dates

[mekarpeles]

Closes #8351

The PR makes a statement that no created record from any source should have a future date.

Most records with future dates will fail to import because of the validation step. Records from sources that are exempt from validation, like bwb promise items, will have certain fields checked/pruned during the normalize stage.

Technical notes

All API imports (I'm not sure about /addbook though, which does have front-end validation) seemingly go through https://github.com/internetarchive/openlibrary/pull/8367/files#diff-2f9a6b1879442fc58af3064df91b70cd3138d6da15003d0d3127ecf05098386cL975-R997. Everything goes through validate unless (currently) it's a promise item, in which case validate is skipped. Everything should go through normalize after, including promise items.

TODO

• ⚠️ /addbook should fail gracefully if/when a POST with future date. Currently id doesn't
  • This shouldn't be a blocker because https://github.com/internetarchive/openlibrary/blob/master/openlibrary/plugins/upstream/addbook.py#L78-L95 doesn't seem to use the catalog flow and instead seemingly just creates new documents. We may want to DRY up these flows as per Basic DRY refactoring of Catalog Import into testable pieces #7701
  • This seems like a separate task and the current PR seems to do what we want.
• A test would be useful (of a promise item that includes invalid date) getting created w/ invalid date removed

[scottbarnes]

I updated the key for publish_date, added unit tests, and tested importing with a a current or past date, and a future date, in the local dev environment, and everything seems to be working as expected in terms of future dates being removed, and it not appearing to create any downstream errors (e.g. the Work and Edition page render properly with a deleted date).

[cdrini]

Lgtm ! Patch deploying since this is causing issues in the import pipeline for archive.org