Problem/Motivation
Conceptually it makes sense for the history module to support any entity type, but historically it only supports node.
Proposed resolution
The service introduced in #3267010: Introduce a generic HistoryRepository service without changing storage or caching provides an API that supports any entity type.
Alter the history storage to support entity types other than node.
Remaining tasks
User interface changes
None.
API changes
None.
Data model changes
Alterations to the history table.
