Get node lock message "The content has either been modified by another user..." when editing a node published by scheduled_transitions with "recreate pending revision" enabled

Problem/Motivation

After a node is published by scheduled_transition with the option "Recreate pending revision" enabled, I am no longer able to edit that node because of the error message "The content has either been modified by another user, or you have already submitted modifications. As a result, your changes cannot be saved.".

Steps to reproduce

* Create a draft revision (A) of a node. This revision is the latest revision.
* Schedule to publish that revision A: select the revision ID from Scheduled Transitions dialogue, not the "Latest revision" option (with "Automatically determines the latest revision at time of transition"), tick the checkbox "Recreate pending revision"
* Create another draft revision B
* Run cron to trigger scheduled transitions.

Expected results

* The node is published with content from revision A.
* The latest revision is not published and has content from revision B.
* The node can be edited and saved without any error.

Actual results

* The node is published with content from revision A.
* The latest revision is not published and has content from revision B.
* The node cannot be saved because of the error message "The content has either been modified by another user, or you have already submitted modifications. As a result, your changes cannot be saved.".

This issue occurs on both version 8.x-1.1 and 2.0.0.

Debugging

Looking at the node_field_revision table:

* The revision A to be scheduled for publishing is vid #52153.
* The revision B is vid #52154
* Scheduled Transition copies #52153 to #52155 and publishes it (expected).
* Scheduled Transition copies #52154 to #52156 as the latest revision and set it as draft (expected).
* However, the latest revision #52156 has the same changed timestamp (1619503497) with #52154, whereas the current revision #52155 has a newer changed timestamp (1619503557).
* The latest revision has an older timestamp than the current revision, hence it triggers the EntityChanged constraint upon node edit form submission.