[Draft] Add database reset on Ephemery Network

[gconnect]

PR Description

• Add deposit chainId to the generated network.yml file
• Reset the db

Todo

• Still need to ensure that the above only happens on Ephemery

Doing this tends not to work as expected

  final Eth2NetworkConfiguration networkConfig =
        Eth2NetworkConfiguration.builder(Eth2Network.EPHEMERY).build();

    if (networkConfig.getEth2Network().equals(Optional.of(Eth2Network.EPHEMERY))) {
      ....
    }

Still figuring how to handle the check.

Fixed Issue(s)

"fixes #8589"

Documentation

• [ ] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• [ ] I thought about adding a changelog entry, and added one if I deemed necessary.

[gconnect]

@rolfyone please take a look when you have the time.

[rolfyone]

Thanks for raising, will review shortly. One initial comment - We'll only want 'partially addresses' in the 'fixes, because this would otherwise close the issue...

[gconnect]

Thanks for raising, will review shortly. One initial comment - We'll only want 'partially addresses' in the 'fixes, because this would otherwise close the issue...

Not sure what you meant here.

[gconnect]

We could potentially treat this as a 'tracer' PR and just create a new branch with what we want in the first one... Alternatively we need to remove all of the functionality other than the network yaml change Basically, I need a PR that just changes the network yaml and doesn't break anything when reading the old configuration file that doesn't have the chain id in it... This is really critical, because thats basically ensuring its not a breaking change.

What changes will I apply to the network.yaml file if I am not adding the chainId?

[gconnect]

opened a new PR here https://github.com/Consensys/teku/pull/8631