Blocks backfilling option - 4 Peers tracker optimization

[abi87]

How this works

Backfilling is split in the following PRs

• [X] Introduce new interface as well as empty implementation to unlock compilation. See https://github.com/ava-labs/avalanchego/pull/2343
• [X] Implement block retrieval in engine, via GetAncestors. See https://github.com/ava-labs/avalanchego/pull/2144
• [X] Implement backfil handling in proposervm. Mind need to rebuild backfilled blocks list upon restart (see https://github.com/ava-labs/avalanchego/pull/2241)
• [X] Implement backfil in coreth. See https://github.com/ava-labs/avalanchego/pull/2255
• [X] Experiment with bandwith aware peer tracker to speed up blocks download.

How this was tested

CI + successful mainnet sync with https://github.com/ava-labs/avalanchego/pull/2273 code

[github-actions[bot]]

This PR has become stale because it has been open for 30 days with no activity. Adding the lifecycle/frozen label will cause this PR to ignore lifecycle events.