Conflict resolution on entity level

[novoj]

This issue is a part of larger issue #503. It introduces default conflict resolution strategy on entity level. So that no two concurrent transactions may upsert/remove same entity. Also no two concurrent transactions are allowed to execute schema altering mutation to the same catalog.

These levels will become default for future expanding of evitaDB capabilities.