Handle bitshares-report

[bitshares-report](https://github.com/bitshares/bitshares-report) is being used for ES history export.

This needs maintenance with latest ES changes, as well as some bugfixes I have found during creating reports for individuals.

Options:
a) fix bitshares-report and upgrade dependencies (estimation is at least 4h), requires publicly available ES
b) remove export from UI without replacement, possibly include links to external services
c) use external service for history export (e.g. blocksights or others?)

Thoughts @abitmore ?

Start with the bitshares-report project and the history-export path in the UI, then compare its current behavior with the latest Elasticsearch changes. The issue is done only after choosing one of the three export strategies, implementing or removing the UI path accordingly, and verifying history reports work or the replacement links are available.

Written by the indexing model from the issue text.