Custom ports cause incorrect YAML configurations

[Batimius]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing issues and didn't find any that were similar
• I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

When using custom ports for the SYNC_* services, it causes all configuration files to have a wrong network / node configuration. It ignores the ports that were set and removes the quic addresses. This does not only happen on the client.yml, but on the config.yml of the individual services as well.

Expected Behavior

It should utilize the ports provided in the .env.override file (which gets merged into the .env file) and have the correct configuration.

Steps To Reproduce

1. Follow steps listed in the README
2. Use the following overrides:

ANY_SYNC_NODE_1_PORT=66711
ANY_SYNC_NODE_1_QUIC_PORT=66721

ANY_SYNC_NODE_2_PORT=66712
ANY_SYNC_NODE_2_QUIC_PORT=66722

ANY_SYNC_NODE_3_PORT=66713
ANY_SYNC_NODE_3_QUIC_PORT=66723

ANY_SYNC_COORDINATOR_PORT=66714
ANY_SYNC_COORDINATOR_QUIC_PORT=66724

ANY_SYNC_FILENODE_PORT=66715
ANY_SYNC_FILENODE_QUIC_PORT=66725

ANY_SYNC_CONSENSUSNODE_PORT=66716
ANY_SYNC_CONSENSUSNODE_QUIC_PORT=66726

3. Run make start

Environment

- OS: Ubuntu 24.04.4 (GNU/Linux 6.8.0-101-generic x86_64)
- Version: `prod`

Anything else?

No response

[Batimius]

It looks like the issue was caused by the fact that I changed the ports after I had ran make start once, which I assume conflicted with the generated files in the storage directory. The make cleanEtcStorage command does not take into account the enviromental variable STORAGE_DIR and just deletes the directory at ./storage (#180). A clean install (removing all files / images / volumes and cloning the repo again) fixed the issue.