[EW] Version history update is delayed

When a content manager works on a document, they don't see the new version created in the history. It will be updated only after a full page refresh

Reproduce the issue by having a content manager create a document version and checking the version history before and after a full page refresh. Trace the version-history update path and verify that the newly created version appears without requiring a refresh; the issue names no files or tests to start from.

Written by the indexing model from the issue text.