Don't update k8s-settings object, if already present

[0sewa0]

Description

K8S-11513

If we update the k8s settings object that already exists, for some reason causes data gaps.

We should avoid updating it, as it was done before v1.3

The diff looks a bit confusing:

• I just moved the settings.TotalCount > 0 check(and related calls) , before the r.dtc.CreateOrUpdateKubernetesSetting(... call

How can this be tested?

There was a unit-test that was supposed to test for this.

• I fixed it, now it fails with the old logic

Otherwise you have to make it update, and see gaps in the collected data