Add claimed_id for child nodes streamed to their parents

[underhood]

Summary

claimed_id of nodes is streamed to parents. For easy testing also added to /api/v1/info (where cloud will need it anyway sooner or later)
Example of 3-level streaming from the view of top-level parent:

Component Name

Streaming

Test Plan

Have some streaming setup and look at /api/v1/info. Check nothing breaks with Cloud by connecting this node to staging.netdata.cloud. Claim nodes and see if their claiming Id propagates up the network by checking /api/v1/info of the topmost node. All nodes have to be running this PR for it to work.

What was tested together with the cloud team:

1. Claim node to Staging and connect it. Node had 2 children.
2. Message as per screenshot above (with new mirrored_hosts_status field) is send to cloud as part of onconnect payload over ACLK
3. Checked Cloud GUI still works as expected with this new fields
4. Cloud team checked there are no errors in the background (not visible to us from GUI)

What was tested additionally:

• node that is claimed during runtime and then netdatacli reload-claiming-state
• up to 4 level hierarchy of streaming
  • TopLevelMaster (VM,not claimed)
  • timowss (real machine,claimed) -> TopLevelMaster (VM)
  • Fed32-Layer1Host1 (VM,claimed) -> timowss (real machine, claimed)
  • Fed32-Layer1Host2 (VM,not claimed) -> timowss (real machine, claimed)
  • Fed32-Layer2Host1 (VM,not claimed) -> Fed21-Layer1Host1 (VM, claimed)
  • this represents final test with biggest amount of hosts tested, during development and testing different combination of nodes and claiming states were used
• both claimed and unclaimed nodes have correct status reported

Additional Information

Codacy false triggers here. It doesn't seem to recognize rrdhost_foreach_read macro is a loop and as a result, thinks if(count > 0) { is always false (which is not true).

[amoss]

Overall it looks ok, I know it is still [WIP] - I'll do a review after the version negotiation changes.

[underhood]

@amoss

this is topology of the 4 layer test However during testing I tried different combinations (especially with claiming/unclaiming nodes) and topologies

[amoss]

Ok good, now the test plan is comprehensive. I'll let the other reviewer take a look before I go back for a second look at the code.

[amoss]

I've disabled the Codacy warnings as they are just noise - it does not understand the loop macro for some reason.

[underhood]

@Ferroin arch CI build started failing yesterday with unrelated error:
configure: error: libuv required but not found. Try installing 'libuv1-dev' or 'libuv-devel'.

Can you take a look if you have 5'

stale

[underhood]

I checked also with production that it doesnt kill something just to be paranoid before merge.