Pass block creation candidate transaction list to plugins

[fab-10]

PR description

Pass candidate pending transactions to plugins

Summary

Provides plugins with visibility into the public transaction pool during block creation by passing the list of candidate pending transactions to the plugin transaction selection API.

Changes

• Modified TransactionSelectionService.selectPendingTransactions() to include a candidatePendingTransactions parameter containing the list of transactions from the public pool

Motivation

Plugins can now see the full context of available transactions in the public pool, enabling better decision-making for custom transaction selection logic.

Breaking Changes

• Plugin API: PluginTransactionSelectorFactory.selectPendingTransactions() signature changed - plugins must update to accept the new candidatePendingTransactions parameter

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.

[Copilot]

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

[daniellehrner]

Some clarifying questions about removed tests and if the breaking change is really neeeded.

Also the changelog entry is currently missing. If we go with the breaking change, we need it and ideally also show a migration path, with an example or a text description