ConfigService does not throw optimistic Lock excepiton if sequenceService updated the doucment

[rsoika]

Scenario:

User-A open System config (sequence Number= 1000)
User-B creates a new Workitem (sequence Number= 1001)
User-A saves System config
NOW again sequence Number= 1000 !

A optimisticeLock Exception is expected but did not occur

Solution:

The reason for this behaviour is that the ConfigService is a Singleton. This means that the VersionID is correctly updated from the internal perspective but not provided after an update.

But we need to avoid that in this situation for example the Sequencenumber can be overwritten. Therefore we need to update the $version