Pagination support and other improvements for custom_operations_api::get_storage_info API

[abitmore]

User Story

As an API node operator and an API user I would like the custom_operations_api::get_storage_info API supports pagination

• as optional parameters (see Review all APIs, add new optional parameters and change some old parameters to optional #1766) and
• with configurable limitation (see BTS PR 1733: Make more API limitations configurable #1903).

Other desired improvements (perhaps need new APIs) are:

• Ideally there should be an API to list all available catalogs, and / or an API to retrieve data without accurately specifying the catalog (E.G. query for all, or do range query), since with current API users need to know the exact catalog to be able to retrieve data.
• Ideally there should be an API to retrieve data from multiple catalogs.

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.)
• 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

[abitmore]

AFAIK @oxarbitrage is working on this, so assigned him.

[abitmore]

Implemented most of the features listed in OP with #2620, except for the "an API to list all available catalogs" (which was implemented in #2144 but not merged).