Uniform notification to selectors on a bundle selection rollback

[fab-10]

PR description

When selecting groups of related txs for block creation (aka bundles), a potential previously selected tx in the group, could be later not be selected anymore, due to the result of following txs in the same group.
This behavior, that is the result of the rollback of the group of txs, has a gap in the notifications sent to selectors, including plugin selectors, since in case of a rollback, only the onTransactionNotSelected method is called on the not selected tx of the group, while for selected but pending commit, but then reverted txs, that same method is not invoked.

This PR fixes this gap, calling also the onTransactionNotSelected method, with not selected reason SELECTED_ROLLBACK, for selected but pending commit, but then reverted txs.
The notification are always sent in the order they are processed.

Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• spotless: ./gradlew spotlessApply
• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests
• hive tests: Engine or other RPCs modified?

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.