(OraklNode) sync roundId based on max suggested id

[nick-bisonai]

Description

RoundId generation

AS - IS

Each peer was generating roundId based on timestamp from each machine. Since each machine could have difference with its generated timestamp, they could've been submitting to different roundId at same tick

TO - BE

This update adds publishing & subscribing layer to synchronize roundId

1. Generates roundId based on timestamp from each peer
2. Publish generated roundId
3. Collects roundIds from subscribed messages
4. Once collected roundIds exceeds number of subscribers, select max value among collected roundIds and proceed

Other updates

• Now receive message also from itself and updates data only from subscription. If data update happens both from subscription and publish, it's difficult to handle conditional execution
• Limited length of roundID string to 6
• Refactoring based on phase of communication. (function extraction, type separation)

Is it okay?

What if there's a disconnected peer?

I assume that condition checking as followed will also be affected as # of subscribers will decrease.
len(n.Data.SuggestedRounds) > n.getSubscribersCount()

What if there's a disconnected peer but still running?

Currently, node is running(publishing) conditionally only if there's 1 or more connected peers.

What about other fallbacks?

Please list down all edge cases that should be handled
It'll be updated in further PRs
Please help 🥹

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.

Deployment

• Should publish npm package
• Should publish Docker image

[martinkersner]

LGTM!