Impossible to save a pending revision as the default one without creating a new revision

Problem/Motivation

This problem was surfaced in the Workspaces module, and it seems to be a regression from the behavior change introduced in 📌 Define 'original' as property on the entity object Needs work . Quoting from that issue's change record:

Note the slight behavior change when saving non-default revisions. Previously, the original property was always the unchanged default revision, now it is the revision that had been loaded, so when saving a new non-default revision based on a previous non-default revision or updating it, changes can be correctly detected.

When publishing a workspace, we are re-saving the latest workspace-specific revision as the new default revision for each tracked entity. This mostly works at the moment because we're also manually setting the default revision on the original property.

However, this breaks for entities that follow the revision status of their "parent", but aren't themselves tracked by the workspace (e.g. revision references to a paragraph), because the workspace publisher can't set the original property on them.

Additionally, after that issue, we should be setting original to be the latest revision itself, not the default one.

Steps to reproduce

Reproducing the issue involves using Workspaces, Paragraphs, and ERR with the patch from 🐛 Incorrect manipulation of default revision flag Needs work . Manual steps would be quite involved and difficult to follow, but the test coverage added here shows the problem quite well.

Proposed resolution

Allow pending revisions to saved as the default one "in-place", without having to create a new revision.

Remaining tasks

Review.

User interface changes

Nope.

Introduced terminology

N/A

API changes

Nope.

Data model changes

Nope.

Release notes snippet

N/A