Remove multiple best tip blocks for actions, if they exist

[MartinMinkov]

Description:

This PR addresses an issue with fetching action data in the case where multiple blocks are returned at the best tip. It introduces a temporary fix that filters out blocks at the best tip, ensuring that we only work with a single best tip block.

Changes:

Added distanceFromMaxBlockHeight to the blockInfo object in the FetchedActions type and in the getActionsQuery.
Implemented a temporary fix that filters out multiple best tip blocks, if they exist, while fetching actions. This fix will be removed once the related issue in the Archive-Node-API repository (o1-labs/Archive-Node-API#7) is resolved.
This change helps improve the reliability of fetching action data and ensures that the fetched data is consistent with the latest network state.

[Trivo25]

Nice! Quick and simple fix

This fix will be removed once the related issue in the Archive-Node-API repository (o1-labs/Archive-Node-API#7) is resolved

I wonder if it's worth waiting, whats the estimate on that?

[MartinMinkov]

Nice! Quick and simple fix

This fix will be removed once the related issue in the Archive-Node-API repository (o1-labs/Archive-Node-API#7) is resolved

I wonder if it's worth waiting, whats the estimate on that?

Good question! To implement the best-tip selection algorithm that's used, we need a redeployment of Berkeley to happen. The Archive Node schema needed two required fields to compute the algorithm, so currently, we can't do it. Once we redeploy Berkeley and migrate the block data for the old blocks, we can implement the algorithm.

Seems worth it to implement this fix right now and then patch the fix once Berkeley is redeployed :)