Avoid to read whole entities to check ETag

Currently, in order to check ETag to provide simple locking for concurrent updates via REST, the whole entities (users / groups / any objects) are read.

This involves internal fetch of a whole set of unused data, some of them (virtual attributes, dynamic memberships) being particularly onerous.