Improve new version push handling

Currently if a new version of an asset is pushed without history information, there will be an error because the backend will try to create an asset from scratch. This will trigger an error because of an already existing asset.

As a side effect, if no asset of a previous version exists, the backbend will create a new one based on the name but with the wrong number.