refactor: unify code paths for receipts removal

[klkvr]

Unifies code paths for receipts removal which is happening in take_state_above (used by legacy engine and ExecutionStage unwind and in remove_state_above (used by new engine and unwind through cli)

New function DatabaseProvider::remove_receipts_from is introduced which accepts the starting receipt number to remove and StorageLocation and removes receipts from database/static files

This PR also includes a fix for take_state_above which might've returned incorrect receipts data in ExecutionOutcome if receipts were removed from database. It did not account for receipts being pruned or moved to static files.

[mattsse]

thread 'stages::execution::tests::sanity_execute_unwind' panicked at crates/stages/stages/src/stages/execution.rs:1069:18:
called Result::unwrap() on an Err value: DatabaseIntegrity(NippyJar("Pruning should be committed before appending or pruning more data"))

[klkvr]

thread 'stages::execution::tests::sanity_execute_unwind' panicked at crates/stages/stages/src/stages/execution.rs:1069:18:
called Result::unwrap() on an Err value: DatabaseIntegrity(NippyJar("Pruning should be committed before appending or pruning more data"))

fixed in 45dee0e

had to apply similar refactor for ExecutionStage consistency checks as in #12743

• missing_static_data_error is now reused between body and execution stage
• prepare_static_file_producer logic moved to ExecutionStage::ensure_consistency and checks the current unwind target like BodyStage::ensure_consistency

[mattsse]

lgtm