Remove NextNodeId from config.txt if version of hedera is >= 0.56

[jeromy-cannon]

As of release 0.56, the use of nextNodeId in the config.txt is going away. The PR for this code change is here: hashgraph/hedera-services#15791
Config files which are automatically generated in software upgrades through DAB are automatically correct.
How does this impact you?
In release 0.56 and later you will need to remove the field nextNodeId from any stored config.txt files and any tools which render config.txt files.

Tasks

Preview Give feedback

1. update the profile_manager.ts prepareConfigTxt() method condition to exclude adding the nextNodeId if the releaseVersion.minor is >= 56
2. the config.txt generated by Solo should not add the nextNodeId into the file

NOTE: as mentioned above, when we copy the config.txt from the nodes ${constants.HEDERA_HAPI_PATH}/data/upgrade/current/config.txt, it will already be correct, so no updates are needed for these.

[swirlds-automation]

🎉 This issue has been resolved in version 0.32.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀