API improvement: creating a new version

[avivace]

While playing with versions with the API with @carmenmarcos00, we found some confusion on what it really means to create a version from a specific Record ID:

1. From the UI, you can create a new version from any of the published versions of a Record. Depending on which one you choose, the schema of that "source" version will be picked and data pre-populated from there. It is kind-of implied that you are actually creating a version C from a version A, when in reality, this order is not "maintained" nor exposed or saved anywhere, and if you have a more recent version of the record (e.g. B), the new version will follow B, not A, even if you created the version from A.
   • Maybe this could be clarified when people try to create version from a non-latest one.
2. From the API, a Record ID is required to create a version, even if - in practice - the route implementation will look for the most recent version anyway, ignoring the passed ID, which is then used just to find the more recent version.
   • At that point, maybe it makes more sense to make people create new version targeting a Parent id (since that one is created on the first publish and stays the same for all versions)?