Improve and document how to work with detached test plugins project

[fab-10]

PR description

This PR is a followup to #9590, and add documentation on how to work on the detached test plugins plus some more automation

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.

[usmansaleem]

LGTM. Do we need to add any additional information regarding upgrading of this gradle wrapper whenever we upgrade root project's gradle wrapper?

[fab-10]

LGTM. Do we need to add any additional information regarding upgrading of this gradle wrapper whenever we upgrade root project's gradle wrapper?

That's a good point, and it will be nice to have an automated way to warn if the gradle version is not aligned with the main project, I will think about it.