Turned PostMergeContext to be a regular class instead of a singleton.…

[Filter94]

… Addded some other improvements to the acceptance tests DSL

PR description

Fixed Issue(s)

This fix allows ThreadBesuNodeRunner to spin up and tear down Besu instances multiple times during process's lifecycle.

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

[Filter94]

Please note this change. I couldn't find a better way to get around this and I wonder if there's a better way

[Filter94]

I need a tip on this part. ThreadBesuNodeRunner can only create a Besu instance that doesn't have persistence, meaning it's losing all the state after restart. In-memory KeyValueStorageProvider is provided by BesuControllerModule::provideKeyValueStorageProvider called by dagger. I wonder if there's a non invasive way to invert this dependency and provide a different key value storage, namely I'd like to set it to a persistent version for my testing.

[macfarla]

@jflo thoughts on dependency nuances here?

[jframe]

Overall I think the PR can be simpler by just reusing the consensusContext from the MergeBesuControllerBuilder.

I had a go at doing this by creating it up front in the MergeBesuControllerBuilder and exposing a getter for the TransitionControllerBuilder still a bit ugly but it hides the details in the controller builders.

Here's my attempt if you want to take a look #8253

[jframe]

I think this can be simpler. There is no need to expose the PostMergeContext as a method in the BesuControllerBuilder as we are already building this in the createContext method

[Filter94]

Consumed by this PR