[tracker] Collateral Management Service

[LayneHaber]

Things needed for 3rd party collateral management services.

• Scaffolding for rebalancing service #788 Scaffolding including a django app that has the following API endpoints

1. getTargets(hashOfXpub: string) => 
{ 
  collateralize: [
    <ASSET_ID>: {
      upperBound, // collateralize up to this
      lowerBound // when this hits, collateralize, then re-request bounds
    }[]
  ],
  reclaim: [
   <ASSET_ID>: {
      upperBound, // when this hits, reclaim, re-request bounds
      lowerBound // leave this much in the channel
    }[]
  ]
}

2. getDisputes() => string[]

• [collateral, node] Create endpoint to pull data to API #791 Node endpoint to pull data to the API
• [node] Onchain transactions #792 Make sure deposit/withdrawals/etc. are tracked in onchain_transactions
• [node] Anonymize transfer data #793 Node should create a view for the service with anonymized transaction/payment data
• [node] Deprecate requestCollateral #794 Replace all requestCollateral calls in node to request from service + update logic (including fallback logic)
• [client, card] Remove requestCollateral #795 Remove requestCollateral from client API
• [collateral] Create db for collateral service #796 Service should have its own database that it can query + update from node data (have onchain_transactions and transfers views)
• [collateral] Service auth #797 Token/simple bearer auth for service (also generate API Keys for clients)
• [node] Remove paymentProfiles from node #798 Remove paymentProfiles from node
• [node] Out of model transfers #799 Make sure node can handle unusually large payments (outside of targets returned from service)
• [collateral, node] Reclaim via disputes #800 Node endpoint to get list of all xpubs it should dispute + set up nightly tasks
• [collateral] Deployment and CD/CI setup #801 Deployment and CD/CI of collateral management service