Drop head tracker for summaries DAG

[dapplion]

Issue Addressed

The head tracker is a persisted piece of state that must be kept in sync with the fork-choice. It has been a source of pruning issues in the past, so we want to remove it

• see Remove head tracker in favour of fork choice #1785

When implementing tree-states in the hot DB we have to change the pruning routine (more details below) so we want to do those changes first in isolation.

• see Database growth during non-finality #6580
• If you want to see the full feature of tree-states hot HDiff in the hot DB dapplion/lighthouse#39

Closes #1785

Proposed Changes

Current DB migration routine

• Locate abandoned heads with head tracker
• Use a roots iterator to collect the ancestors of those heads can be pruned
• Delete those abandoned blocks / states
• Migrate the newly finalized chain to the freezer

In summary, it computes what it has to delete and keeps the rest. Then it migrates data to the freezer. If the abandoned forks routine has a bug it can break the freezer migration.

Proposed migration routine (this PR)

• Migrate the newly finalized chain to the freezer
• Load all state summaries from disk
• From those, just knowing the head and finalized block compute two sets: (1) descendants of finalized (2) newly finalized chain
• Iterate all summaries, if a summary does not belong to set (1) or (2), delete

This strategy is more sound as it just checks what's there in the hot DB, computes what it has to keep and deletes the rest. Because it does not rely and 3rd pieces of data we can drop the head tracker and pruning checkpoint. Since the DB migration happens first now, as long as the computation of the sets to keep is correct we won't have pruning issues.

[dapplion]

@michaelsproul If we stop updating the head_tracker in the persisted head, how can we downgrade safely? If you run an old version of Lighthouse it will read the persisted head which contains an empty head tracker.