Use actual revision user when updating an existing entity

[TheETupper]

When an automated process (e.g. harvest) creates a new revision of a dataset, it will always use the author of the latest revision for the next node revision.

https://github.com/GetDKAN/dkan/blob/2.x/modules/metastore/src/Storage/Data.php#L311

https://github.com/GetDKAN/dkan/blob/2.x/modules/metastore/src/Storage/Data.php#L342

$entity = $this->getEntityLatestRevision($uuid); // Uses the last revision as the base, including the revision_uid
...
return $this->updateExistingEntity($entity, $data); // Calls update function
...

// From updateExistingEntity()
if ($entity instanceof RevisionLogInterface) {
// Only sets new values for the revision time and log message; revision user remains what it was
$entity->setRevisionLogMessage("Updated on " . (new \DateTimeImmutable())->format(\DateTimeImmutable::ATOM));
$entity->setRevisionCreationTime(time());
}
This issue with the revision author defaulting to the last one only applies to data nodes that are updated by an automated process. It is not an issue with user-edited nodes like book pages.