[2][manikey123] Ensure back end API changes reflected to front end based on config file updates

**Is your feature request related to a problem? Please describe.**
Backend changes to config ini is being made and its reflection to frontend needs to be evaluated/fixed. Will be better placed to work / update this ticket once the core tickets complete ( around February)
**Describe the solution you'd like**
Inspired from core ticket : 782, 783
https://github.com/bitshares/bitshares-core/issues/782
https://github.com/bitshares/bitshares-core/issues/783

Some API's under scope ( will revist this list once core tickets are pushed):
get_grouped_limit_orders
get_asset_holders_count
get_asset_holders
get_account_history_by_operations
get_relative_account_history
get_fill_order_history
get_key_references
get_limit_orders,
get_call_orders,
get_settle_orders
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
Based on backend changes
**Additional context**
Add any other context or screenshots about the feature request here.


Start by reading core issues 782 and 783 and reviewing the configuration INI changes they describe. Then revisit the listed APIs and identify how each backend change should be reflected in the frontend; the work is done when the affected API behavior and configuration updates are represented consistently in the UI.

Written by the indexing model from the issue text.