interledger-ccp API review for v1.0-rc

[gakonst]

interledger-ccp public items marked with x are documented. Non-exported items are not taken into account. Follows format from #561.

Part of #557.

• CcpRoutingAccount (trait)
• RouteManagerStore (trait):
  • Should this be renamed to CcpRoutingStore? That would make it consistent with how the other Account/Store pairs are named.
• RoutingRelation
• Mode
  • We never use Idle mode. Should we remove Mode altogether and assume Sync? Added the first draft of Route Broadcasting Protocol rfcs#455 is closed and seems stale atm, so I am not sure what's the path towards CCP standardization
• RouteControlRequest
  • Should to_prepare be implemented as Prepare::from(src: RouteControlRequest)?
• RouteProp
  • Should we convert it to pub(crate)?
• CcpRouteManager
• CcpRouteManagerBuilder: Does this need to be documented? Its fields are docuemnted, and given that it's a builder its functionality should be intuitive.

[bstrie]

• I'd say yes to the rename of RouteManagerStore.
• No opinion on Mode, do whatever seems most conservative.
• If RouteProp can be made pub(crate), then absolutely. Reducing the public surface area is good.
• CcpRouteManagerBuilder: Even just a line saying something like "See documentation on fields" would be nice to show that documentation wasn't just forgotten about.

[gakonst]

• Renamed to CcpRoutingStore
• Mode has been left as is, for potential future implementation of the Idle feature, since it's implemented in the js connectors
• RouteProp is now pub(crate)
• Added a small comment on CcpRouteManagerBuilder