Fix receipt recovery & migration

[emlautarom1]

Fixes #5823

Changes

• Use AncientReceiptsBarrier as lower bound when fixing receipts.
• Properly calculate receipt.ContractAddress by recovering sender.

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• [] No

Notes on testing

Added unit test and also tested against user provided scenario on a running client.

Documentation

Requires documentation update

• Yes
• No

Requires explanation in Release Notes

• Yes
• No

Remarks

It would be nice if we could create a unit/integration test for the associated ticket.

[emlautarom1]

syncConfig.PivotNumberParsed delegates to syncConfig.PivotNumber, which is not a read-only field. The pivot number is modified here:

nethermind/src/Nethermind/Nethermind.Merge.Plugin/Synchronization/PivotUpdator.cs

Line 77 in 52d7add

_syncConfig.PivotNumber = updatedPivotBlockNumber.ToString();

then, by the time that this code gets executed, the pivot number is not what the user originally configured.

---

Either way, we should use the AncientReceiptsBarrier value for this operation.