Making 10 changes without publishing causes version conflicts

## Gentics Mesh Version, operating system, or hardware.
- v1.4.3

## Operating System
- Linux

## JVM
- OpenJDK 11.0.5

## Problem

I'm new to this, just exploring the demo (with `docker run -p 8080:8080 gentics/mesh-demo:1.4.3`) to determine whether we could use mesh for one of our projects. I noticed a small problem:

When I make changes to a node, the minor version is incremented, e.g. from 1.0 to 1.1 to 1.2 and so on, for every change. After clicking "Save" on 1.9, I don't see the minor version increasing, and then clicking save again, the following dialog appears:

> Resolve conflicts: 1.10 / 1.9
> Your changes conflict with the saved version on the server.
> [Cancel] [Save Changes]

After clickign the "Save Changes" button, a notification says "Node successfully saved", but the version is still shown at 1.9. When clicking "Save" again the dialog appears again.

By clicking "Publish" the major version goes to 2.0, and the problem goes away.

## Expected behaviour and actual behaviour

I would expect the minor version to go to 1.10 without causing a "conflict".

Edit: It appears to be a bug in mesh-ui. When I make changes with a POST request to the REST API, the version goes 1.10 without a problem.

Reproduce the issue in mesh-ui using the documented Docker demo, making successive node changes through the UI and comparing them with the REST API behavior. Trace the UI's save and version-conflict handling, then verify that ten unsaved minor-version changes can be saved without a conflict and that the displayed version reaches 1.10.

Written by the indexing model from the issue text.