Add API for exporting certificate chain for Filecoin snapshots

[Stebalien]

Meta

This issue used to be the placeholder for "augmenting Filecon snapshots with F3 information". Since Forest owns Snapshot creation/publishing for the network, they are taking the lead here and that work is being tracked in ChainSafe/forest#5627 .

This issue has been downscoped to just cover the work needed in go-f3. Lotus and Forest items will be in their respective repos.

Specifically what's needed from go-f3

API for exporting the certificate chain so that Forest and Lotus snapshot generation code can include the certificate chain in their exports per the to-be-designed snapshot format.

Information before this issue was downscoped

We need to store the following in our Filecoin snapshots once we pass the F3 bootstrap epoch.

1. The current F3 manifest.
2. The power table for the bootstrap epoch - 900.
3. All finality certificates we currently have.
4. Power table deltas for all epochs between the last finality certificate and the first epoch included in the snapshot (if any). This should only be required if F3 falls behind EC.

• I've dropped the F3 manifest because this will be baked into clients (normally). This will cause a few issues when testing (nodes may start with the wrong manifest), but they'll quickly receive the correct manifest from the network and switch to it).
• I've dropped the initial power table. Eventually, this will be shipped with clients (first release after F3 genesis) but, for now, it can be fetched over the network given the first finality certificate.

[jennijuju]

Moved to milestone 2 as i dont think this is mandatory for nv23. This needs yo be tracked by chainsafe infra team as well.

[jennijuju]

@Stebalien does lotus import-snapshot logic needs to get updated as well?

[aatifsyed]

Do you have a sketch for a new layout @Stebalien?
It sounds like an increment of the CarHeader version would be appropriate :)

[Stebalien]

We don't need a new car format, just an additional root for the F3 data (which we can IPLDize and store the same way we do the rest of the chain).

This doesn't need to happen before nv23 but, if it doesn't, anyone restoring from a snapshot will be unable to join F3.

[Stebalien]

It's also possible to partially solve this without touching the snapshot format by instead fetching the required information over the network. We still need to change the snapshot format for point (4), but that's less critical.

[Stebalien]

(moving back into milestone 0 until we've actually figured out what to do here)

[Stebalien]

Power table deltas for all epochs between the last finality certificate and the first epoch included in the snapshot (if any). This should only be required if F3 falls behind EC.

An alternative is to require that snapshots include all state up until the last F3 finalized epoch. Unfortunately, if there's an issue with F3 at any point, that could grow.... large.

Given that this is kind of an "emergency measure" kind of thing, we could also just distribute these power tables separately if/when necessary.