Fix: avoid panic in ksm-core ingresses collector

[clamoriniere]

What does this PR do?

• Update kube-state-metrics dependencies to v2.7.0 to benefit from
  upstream fixes.
• Add kube-state-metrics patch on top of v.2.7.0 to make this version
  usage in the kubernetes_state_core check. this patch require to use a
  fork of the upstream project until fix: public Builder compatibility with the BuilderInterface kubernetes/kube-state-metrics#1994 has
  been merged and released.

Motivation

Fix possible panic in the kubernetes_state_core check, when a Kubernetes Ingress object with a resource
instead of a service inside .rules[].http.paths[].backend.

Additional Notes

Possible Drawbacks / Trade-offs

we update from v2.4.2 to v2.7.0 "kube-state-metrics" to benefit from the upstream fix. But it is not the only fix or code change. we need to be careful during the QA of this card on other kubernetes_state.* metrics generation.

Describe how to test/QA your changes

deploy the agent and cluster-agent with kubernetes_state_core enabled.
create an Ingress object with a rule defining using a resource instead of a service in .rules[].http.paths[].backend.
With this fix is should not panic.

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.