Add ephemery network config

[gconnect]

PR description

Fixed Issue(s)

• Add Ephemery genesis file to the resources
• Add Ephemery network to NetworkName
• Add test for Ephemery to BesuCommandTest
• Add Ephemery to NetworkDeprecationTest file
• Add Ephemery genesis function to automatically generate a new genesis file in line with the spec requirements for Ephermery Testnet
• Add test for the genesis generation function

This PR is in response to this issue 7404

@non-fungible-nelson please review when you have some time.

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:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[gconnect]

@macfarla you can go over the requested changes here.

[gconnect]

@macfarla all requested updates have been made.

[macfarla]

ok think it is getting close! a few nits and suggestions on naming

[gconnect]

@macfarla made the requested changes thanks for reviewing.

[gconnect]

@macfarla I am done with all the requested changes please review when you have the time. @Gabriel-Trintinalia please also assist with reviewing when you have the time thanks.

[macfarla]

couple of final comments on the test class, otherwise LGTM

changelog has a conflict

[jflo]

Fantastic contribution, thanks so much. The only thing I would add (doesn't have to be in this PR, would be fine in a new one) is maybe some Ephemery specific logging when the network rolls over. Right now, the user will get:

2024-10-01 08:09:00.429-04:00 | main | ERROR | Besu | Failed to start Besu
picocli.CommandLine$ExecutionException: Supplied genesis block does not match chain data stored in /Users/jflo/src/besu/build/data.
Please specify a different data directory with --data-path, specify the original genesis file with --genesis-file or supply a testnet/mainnet option with --network.

It might be worth adding a line explaining that if Ephemery rolled over, they need to reset their data, and this is to be expected.

[gconnect]

Fantastic contribution, thanks so much. The only thing I would add (doesn't have to be in this PR, would be fine in a new one) is maybe some Ephemery specific logging when the network rolls over. Right now, the user will get:

2024-10-01 08:09:00.429-04:00 | main | ERROR | Besu | Failed to start Besu
picocli.CommandLine$ExecutionException: Supplied genesis block does not match chain data stored in /Users/jflo/src/besu/build/data.
Please specify a different data directory with --data-path, specify the original genesis file with --genesis-file or supply a testnet/mainnet option with --network.

It might be worth adding a line explaining that if Ephemery rolled over, they need to reset their data, and this is to be expected.

@jflo thanks for this. Once this PR is merged the automatic database reset feature is what I will be working on next. That should fix the above issue.

[gconnect]

@macfarla I have made the requested changes.

[macfarla]

@gconnect there's a failing test

BesuCommandTest > ephemeryValuesAreUsed() FAILED
org.opentest4j.AssertionFailedError at BesuCommandTest.java:1877

[macfarla]

Thanks for your contribution on this @gconnect 🎉

[gconnect]

Thanks for your contribution on this @gconnect 🎉

Thanks for reviewing.