Allow for proposals to be built on top of historical revisions

[RodrigoVillar]

AFAIK, SAE aims to support several debug APIs, one of which includes debug_intermediateRoots:

https://github.com/ava-labs/avalanchego/blob/09a9530c3145e3990aac1c920d7d72fea1077873/graft/coreth/eth/tracers/api.go#L540

This call executes each transaction at a given height H and stores the post-execution state root in a list; this list is returned at the end of the API call. If H is the latest block height, this call is successful if using Firewood. However, is H is less than the latest block height (i.e. a historical revision), then calling this API method with Firewood fails as this method will attempt to build a proposal on top of a historical revision, which Firewood currently doesn't support.

Originally, I thought that this was an issue specific to deferred persistence but even in a pre-deferred persistence world, this API call fails.

[rkuris]

What's the use case for this?

[RodrigoVillar]

What's the use case for this?

@rkuris I updated the issue description to include the use case.

[RodrigoVillar]

Note: in the context of deferred persistence, we'll need to the ability to create proposals on top of revisions if we want to increase the commit count on archival nodes while supporting archival queries.