Support for tracking multiple candidate chains

[agaffney]

We need to track multiple candidate chains, one per outbound chainsync client. We'll have one "primary" chain which is stored in the database. Any other candidate chains will track their blocks in memory. Candidate-only blocks should be stored centrally, and chain can iterate over points.