Evict possible cell ref txs before submitting cell consuming transaction

[chenyukang]

What problem does this PR solve?

Problem Summary:

The are conflicts rule between cell dep reference and cell consume relationships.

Assume there are 3 transactions, B cell dep A(and there may be many transactions also cell dep A), C consumes A.

• If C is committed first, B and all other transactions will be invalidated.
• If there are too many transactions all cell dep A, transaction C can not be submitted to txpool.

What is changed and how it works?

This is an alternative solution with #4352
In this PR, we introduce these changes:

• Add a new check_entry_ancestors_limit to find all candidates needed to evict due to cell ref conflicts, based on evict_score.
• Remove DirectParents and direct_ancestors_count, we make sure an entry's ancestors number is valid after evicting conflicted cell ref transactions.
• Move ExceededMaximumAncestorsCount check to place before inserting, so that we can assume there will no error report when committing a entry.

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.