fix: restore multinode mode functionality

[isavov]

Description:

Changes introduced in the consensus node version 0.59.0 have resulted in multinode mode not working. This PR restores the functionality by:

• Converting the old pfx formatted keys and certificates for the additional nodes to pem.
• Updating config.multinode.txt with settings compatible with the newer versions
• Updating ENV variables for the additional nodes.

Related issue(s):

Fixes #1017, Fixes #992

Notes for reviewer:

I did my best to test this PR, but was not able to test it fully. Please test yourself before merging.

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

@@           Coverage Diff           @@
##             main    #1031   +/-   ##
=======================================
  Coverage        ?   60.21%           
=======================================
  Files           ?       29           
  Lines           ?     1204           
  Branches        ?      153           
=======================================
  Hits            ?      725           
  Misses          ?      456           
  Partials        ?       23           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Nana-EC]

Great work. Minor non blocking comments.
I had a PR with similar changes I wanted to push but your changes are focused so let's go with this.
if this works let's get it in and get a new version out and I can circle back with tickets for other things I had in mind.
@georgi-l95 kindly take a look.

[Nana-EC]

Bump @isavov and @georgi-l95

[isavov]

@Nana-EC @georgi-l95 Rereview please 🙏
Pushed some updates, needed to adjust the multinode config - it appears nodes should be defined by ip addresses and not FQDNs.
The other issue was related to mirror node monitor, which needed updates for post 0.59.0 consensus nodes.
In my tests I got some issues with timeouts while starting up, which were resolved by setting the retry attempt to a higher value from the default 100, likes so
FIRING_UP_RETRY_ATTEMPTS=1000 npm run restart -- -d --verbose=trace --multinode

[Nana-EC]

@Nana-EC @georgi-l95 Rereview please 🙏 Pushed some updates, needed to adjust the multinode config - it appears nodes should be defined by ip addresses and not FQDNs. The other issue was related to mirror node monitor, which needed updates for post 0.59.0 consensus nodes. In my tests I got some issues with timeouts while starting up, which were resolved by setting the retry attempt to a higher value from the default 100, likes so FIRING_UP_RETRY_ATTEMPTS=1000 npm run restart -- -d --verbose=trace --multinode

Hey @isavov , nice work.
Just to be clear can you confirm you've been able to publish transactions using the mirror node monitor to all 4 nodes without issues and the transactions went through consensus?
If so then everything is solid 🙌🏾

[Nana-EC]

LG
If we can confirm operation then I think we're good to get this in and unblock users for this mode, then iterate as needed

[Nana-EC]

LG.
Let's get this in and iterate

[georgi-l95]

Works, played around by stoping and starting different nodes to see if they catch up or if the mirror node ingests the record files. Everything is working as expected. Well done and thank you @isavov