Fix node.by_condition metric

[L3n41c]

What does this PR do?

Fix the kubernetes.node.by_condition metric introduced by #9311 to make it have the same behaviour as the kubernetes_state_core check.

Motivation

• The host of the metric were always the host running the agent instead of node concerned by the metric
• Only the “active” (value == 1) metric must be taken into account.

Additional Notes

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• PR title must be written as a CHANGELOG entry (see why)
• Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
• PR must have changelog/ and integration/ labels attached

[codecov]

Codecov Report

Merging #9467 (75e72d1) into master (ee9a3fe) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Flag	Coverage Δ
kubernetes_state	89.69% <100.00%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
kubernetes_state/tests/test_kubernetes_state.py	97.33% <ø> (ø)
...atadog_checks/kubernetes_state/kubernetes_state.py	84.84% <100.00%> (+0.08%)	⬆️