[Follow up] Add Transaction Permissioning Hook to PermissioningService Interface

[relu91]

PR description

This PR builds upon the work started in #7952, finalizing the implementation while maintaining consistency with the existing changes.

Key Updates:

• Completed the feature without altering the previous implementation significantly.
• Added some improvements to the acceptance tests
• Ensured consistency with the existing codebase by following established style and logic.
• Took inspiration from the NodePermissioningController for handling plugin-based submissions, aligning the approach with Besu’s existing permissioning mechanisms.

Basically, after merging this work, people can filter transactions using the PermissioningService in their plugins. I would say adding some examples to the documentation might be useful.

Note: I didn't like the previous acceptance test, I found it a little bit convoluted for simply assigning the filtering mechanism of the plugins. As I said, I tried to be as conservative as I could. If you want, we can discuss possible improvements there.

Fixed Issue(s)

#7835

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

[macfarla]

thanks for your contribution! Strong preference for not modifying the smart contract permissioning code at this stage since it's about to be removed.

[macfarla]

we've deprecated smart contract based permissioning per the sunset plan https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu

so this class is going to be removed

[macfarla]

and right now we're effectively in a code freeze for the sunset features. So would prefer not to modify this code if possible, and if not possible, would prefer to remove smart contract permissioning first.

[relu91]

That was indeed another thing that I wanted to mention in the first comment. I can revert that change. Should I also add @Depracted tag? or is it not common practice here?

[relu91]

Meanwhile, I checked the latest version from main reverting the changes. Let me know if I need to do other cleanups of the previous changes.