[WIP]hydrate record entity from elasticsearch data and use it for display purpose

In fact, I don't see anything specific to Elasticsearch in this implementation. If it's just an alternative to `record_adapter` when record data is not provided by the regular mechanic, why not alter `record_adapter` for this purpose ?
It may be to risky to alter such a core thing considering expectations on legacy code. In such a case may we just have a new `Record` class acting as a proxy to `record_adapter` for legacy code ?