Improve test coverage to reach at least 80% for KMC

[marcobebway]

Description

Improve test coverage to reach at least 80% for KMC.

$ make test-local

?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/cmd     [no test files]
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/env     [no test files]
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/options [no test files]
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/cache       [no test files]
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/edp (cached)
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/gardener/commons    [no test files]
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/gardener/secret     (cached)
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/gardener/shoot      (cached)
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/keb (cached)
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/logger      [no test files]
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/process     (cached)
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/service     [no test files]
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/skr/commons [no test files]
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/skr/node    (cached)
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/skr/pvc     (cached)
ok      github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/skr/svc     (cached)
?       github.com/kyma-project/control-plane/components/kyma-metrics-collector/pkg/testing     [no test files]

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale