The goal is to avoid allocating a new LockOptions instance for each entity instance, which is something we need to do know today for the case the user mutates it.

We should try rethinking the API in such a way that setting lock options is still allowed (of course), but we only allocate a dedicated instance as needed.

The primary reason for this to be expensive was that the LockOptions instance contains a map for the aliases.