Node revision revert behavior is weird when e.g. using paragraphs fields and can not altered

Problem/Motivation

When reverting a (node) revision, the user can chose between reverting only the translatable fields or all fields. While I'm still not happy about the whole kind-of-per-language revision UI, it's especially bad when using paragraphs or another embedded entity, I guess field_collection works basically the same way. IEF when using entity reference revision fields the same I guess.

1. If you chose to only revert this translation, then nothing happens, because the paragraph/reference field is not translatable and the whole field has been skipped.

2. If you revert all fields, then the the reference is reverted back to that old reference, which updates this translation but also reverts all translations back to that state, including deleting translations that were added after that.

Proposed resolution

Not sure, maybe add an event or hook, so that for example entity_reference_revisions can replicate what \Drupal\node\Form\NodeRevisionRevertTranslationForm::prepareRevertedRevision() did for any referenced paragraph.

Remaining tasks

User interface changes

API changes

Data model changes