v2.0: replay: extend last fec set check for 32+ retransmitter signed shreds (backport of #2101)

[mergify]

Problem

When the feature flag is turned on, we need to verify that the last fec set uses the new shred format.

Because the last fec set is not known when receiving shreds, and the new shred format is only used for the last set, we cannot perform this check until replay has completed.

Summary of Changes

Extend the check which compares the merkle roots of the last fec set to additionally check that they are all of the retransmitter shred variant.

---

This is an automatic backport of pull request #2101 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 93edb65 has failed:

On branch mergify/bp/v2.0/pr-2101
Your branch is up to date with 'origin/v2.0'.

You are currently cherry-picking commit 93edb65f7d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   core/src/replay_stage.rs
	modified:   ledger/src/blockstore.rs
	modified:   ledger/src/blockstore_db.rs
	modified:   ledger/src/blockstore_processor.rs

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   ledger/src/shred.rs
	both modified:   sdk/src/feature_set.rs

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[AshwinSekar]

This is the last piece of the duplicate block detection effort, which we hope to rollout in 2.x.
This PR ensures that any frozen bank must be comprised of shreds using the new shred format in the last FEC set when the feature flag is turned on.
The new shred format guarantees that the block has undergone checks to ensure that it is not a duplicate block.

[behzadnouri]

I think we need to first backport #1735 and #1840

[t-nelson]

are we planning to bp #1840

[behzadnouri]

are we planning to bp #1840

yes, but need to backport #1735 first

[behzadnouri]

I think this PR is ready for approval/merge.

[bw-solana]

LGTM

[t-nelson]

@AshwinSekar can you resolve the merge conflict?

[t-nelson]

f now downstream is busted