Map the entire object database (chain state) in ElasticSearch

**User Story**

We have the `es_objects` plugin which copies some data from the object database into ES.

Actually, it seems it is not too hard to map the entire object database in ES, although there might be performance (latency) issues because the object database gets updated frequently.

Not sure if it is worth the effort though.

**Impacts**
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
- [ ] API (the application programming interface)
- [ ] Build (the build process or something prior to compiled code)
- [ ] CLI (the command line wallet)
- [ ] Deployment (the deployment process after building such as Docker, Travis, etc.)
- [ ] DEX (the Decentralized EXchange, market engine, etc.)
- [ ] P2P (the peer-to-peer network for transaction/block propagation)
- [ ] Performance (system or user efficiency, etc.)
- [ ] Protocol (the blockchain logic, consensus, validation, etc.)
- [ ] Security (the security of system or user data, etc.)
- [x] UX (the User Experience)
- [ ] Other (please add below)

## CORE TEAM TASK LIST
- [ ] Evaluate / Prioritize Feature Request
- [ ] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [ ] Perform QA/Testing
- [ ] Update Documentation

Start by reviewing the existing es_objects plugin and how it reads from the object database. Determine whether the full chain state can be mapped in Elasticsearch without unacceptable update latency; the issue does not define more specific files, tests, or acceptance criteria.

Written by the indexing model from the issue text.