feat: HealthManager should be used for all protocol-level & overall health status

[danisharora099]

Problem

For any js-waku consumer, getting to know how to react/respond to certain protocol health status is crucial. Example: if LightPush has 0 peers, while Filter has >0 peers, Filter works for that node while LightPush does not. This is crucial information for the consumer apps that is hard to aggregate and find. For this, we introduced HealthManager

During the last release ([email protected]), we made some hot fixes which in turn removed usage of protocols' peer management out of PeerManager, thus impacting HealthManager's abilities to report correct information.

Solution

Readjust protocols to correctly report data back to the HealthManager.

cc @vpavlin

[weboko]

Ice boxed for now, to be revisited after PeerManager is done.

[danisharora099]

Ice boxed for now, to be revisited after PeerManager is done.

is there an exact issue/milestone that encompasses this work around the PeerManager? can you share? thank you!