Implementing Elastic Search

This is a placeholder issue for tracking implementation of Elastic Search to the UI.

By the end of the current Worker Period (2019-03-01) we should try to complete integrating as much ES features as possible.

### Why ES
Elastic search is a highly dynamic and less resource required searchable database for various data on the chain. Instead of relying on nodes, that can change various parameters at will, we should query Elastic Search servers instead.

## Stage 1
- [ ] Elastic Search Wrapper (https://github.com/bitshares/bitshares-ui/issues/1734)

## Stage 2
Once we have a wrapper able to be queried, these sections can and should be worked upon. They should all still be working even if there is no ES server to query, and fetch data from on-chain.

- [ ] Explore -> Assets
- [ ] Explore -> TX by ID (https://github.com/bitshares/bitshares-ui/issues/354)
- [ ] Dashboard -> Activity (https://github.com/bitshares/bitshares-ui/issues/44, https://github.com/bitshares/bitshares-ui/issues/1665, https://github.com/bitshares/bitshares-ui/issues/1468)
- [ ] Exchange -> My Trades (https://github.com/bitshares/bitshares-ui/issues/68)
- [ ] Exchange -> Market Trades
- [ ] Signup Referrals (https://github.com/bitshares/bitshares-ui/issues/661)
- [ ] Market Search -> Find by Issuer (https://github.com/bitshares/bitshares-ui/issues/1749)

Start with the linked Elastic Search Wrapper issue (#1734), then review the Stage 2 targets listed here: Explore Assets, transaction lookup, dashboard activity, trades, referrals, and market search by issuer. Done means integrating the selected Elastic Search features while keeping each section functional when no ES server is available by fetching data on-chain.

Written by the indexing model from the issue text.