Explain how versioning works with different objects

[MattDodsonEnglish]

It can be a bit tricky to understand when and why certain objects require new versions. An explainer doc could help out, with links from model reference.

[MattDodsonEnglish]

Also explain how Rhize supports or deviates from standard.

[MattDodsonEnglish]

Probably could be three docs: explanation, how-to, reference.

• Explanation template

  # Rhize Versioning
  
  ## Versions in Rhize
  
  <How Rhize versioning works>
  
  ## Why version
  
  ## Compared with ISA-95
  <how and why Rhize deviates>

• How-to

  ## Change versions
  
  ##  Change versions in UI
  
  1. 
  1. ON successs
  
  ## Change versions with GQL
  
  1.
  1. 
  

• Reference

  ## Versioned objects
  
  The following objects support versions
  
  ## Version states
  
  

[MattDodsonEnglish]

These docs should have backlinks from Model reference, and Upsert GQL doc.

[MattDodsonEnglish]

Some version mutations:

• Create_x_version. Creates a new version with the id and version number aligned. Related to Document create operation #63
• Save_x_VersionAs Performs a deep copy of a version and saves it:
• Update_x_VersionState
  • to Draft, Active, Deprecated
  • Rewires the ‘isActiveVersionOf’ relationship