Problem/Motivation
A recent critical issue (#2766957: Forward revisions + translation UI can result in forked draft revisions) brought up the fact the the 'revision_translation_affected' field is basically required for any translatable and revisionable entity type.
Proposed resolution
Let's make the entity field manager provide this field by default.
Remaining tasks
Review.
User interface changes
Nope.
API changes
Nope.
Data model changes
Nope.