[orchestrator] change cardinality of deployment count

[nammn]

What does this PR do?

changes the cardinality count of previous added deployment.count.
Now running deployment.count should return the expected number of deployments without the need to filter_by

Motivation

Before one had to filter_by condition:available, status:true to get the correct count. But users would not expect this when calling deployment.count

Additional Notes

Check looks like this

    {
      "metric": "kubernetes_state.deployment.count",
      "points": [
        [
          1608292794,
          1
        ]
      ],
      "tags": [
        "namespace:default"
      ],
      "host": "agent-dev-nam",
      "type": "gauge",
      "interval": 0,
      "source_type_name": "System"
    },

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 #8222 (881bea2) into master (6e19fd4) will increase coverage by 0.75%.
The diff coverage is 100.00%.

Impacted Files	Coverage Δ
...atadog_checks/kubernetes_state/kubernetes_state.py	85.15% <100.00%> (+0.60%)	⬆️
kubernetes_state/tests/test_kubernetes_state.py	97.19% <100.00%> (+0.02%)	⬆️
coredns/tests/common.py
...dog_checks_base/tests/test_utils_agent_packages.py
consul/tests/consul_mocks.py
elastic/tests/test_elastic.py
...yototycoon/datadog_checks/kyototycoon/__about__.py
datadog_checks_base/tests/test_wmicheck.py
process/datadog_checks/process/lock.py
network/datadog_checks/network/__init__.py
... and 869 more

[mfpierre]

LGTM, minor nit