Asset APIs

**User Story**

As an asset owner I'd like to
* have an API to query histories related to my asset (how users have transacted with my asset), and
* have an API to query detailed distribution of my asset, including balances, orders, collateral, liquidity pools and etc.

**Impacts**
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
- [x] 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)

**Additional Context (optional)**
Add any other context about your request here.

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

No files, tests, or existing API entry points are named. Start by refining the two asset-owner user stories into concrete requirements and identifying the relevant API surfaces for transaction histories and asset distribution. Done means both query capabilities have defined responses, coverage for balances, orders, collateral, and liquidity pools, and tests or documentation describing the behavior.

Written by the indexing model from the issue text.