[Version API] Do not modify source document on new version creation.

[auniverseaway]

If possible, the source document should not be modified upon new version creation.

Additional context

It appears that the source document in question is being modified whenever a new version is created. I do not believe this is necessary, but there is some ambiguity on the current implementation.

A source doc has id & version and both of these are UUIDs. My assumption is that the version UUID is some sort of reference to the most recent version. In order to write this version id in the source, it must be updated, which then changes the modified data.

In an ideal world, we don't need this version UUID in the source doc and we can simply list the versions to determine the most recent version. I'm 99.9% sure we don't use this in UI anywhere or expose it in API, so this is an internal only change.

It's worth noting: our versions are noisy. A customer can easily have 1000+ audits and versions for a source document. So listing to find recent (if we even use this anywhere), may not be feasible. But, again... I really don't think we actually use this version UUID for anything. Same with path... seems risky and imprecise for moves... which, maybe we account for and update the path, but I think everything should be based on that source ID.