fix(mempool): Remove tx immediately during FinalizeBlock success

[mattac21]

Description

Modifies the EVM mempool removal logic when a tx is included in a block to immediately remove it, instead of not removing it and allowing for it to be removed from demoteUnexecutables when it fails a nonce check next block.

This was previously not the behavior, because when removing the tx immediately upon block inclusion via RemoveTx, it would cause all future txs to be dequeued as well. However we have now modified the api of RemoveTx to allow for the caller to override the strict behavior of the pending pool (the option that forces the pending pool to dequeue future txs on removal), so that we can tell the legacypool to not remove future txs in this specific scenario.

To achieve this there would have now been 4 configuration options on RemoveTx, and strict would have had three possible states (nil for default, true to override to true, false to override to false). This felt decently confusing so I did a small refactor to change from passing in true, false, false, to using functional options.

Closes: STACK-1986

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• tackled an existing issue or discussed with a team member
• left instructions on how to review the changes
• targeted the main branch

[linear]

STACK-1986 EVM Mempool remove legacypool tx from evm without having to wait a block