Raise on write conflict in save
The current way to prevent accidental overwrite of the database item is to provide a set of "expected values". This implies to keep track of the original values on the user model side especially when a migration is involved.
To adress this, we will:
- remove the 'expect values' argument
- add a "raise on conflict flag" to replace it.