Add conflicts cache for tx_pool to record conflicted transactions

[chenyukang]

What problem does this PR solve?

Problem Summary:

Starting from 112.0, we don't allow conflicted transactions stay in txpool at the same time, this may have a regression impact for compact block replay, since we reject any double-spending transaction when RBF is disable or RBF check failed.

What is changed and how it works?

We add a new pool called conflicts_cache into TxPool in this PR, we record the conflicted transaction in these scenarios:

1. RBF is enabled, record those replaced transactions into conflicts_cache
2. RBF is enabled, but RBF check rule failed with conflicts, record old transaction into conflicts_cache
3. RBF is disabled, but there is a conflict happening when pre_check, add the new transaction into conflicts_cache after verification.

What's Changed:

Related changes

• PR to update owner/repo:
• Need to cherry-pick to the release branch

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code ci-runs-only: [ quick_checks,linters ]

Side effects

• Performance regression
• Breaking backward compatibility

Release note

Title Only: Include only the PR title in the release note.