fix set node status conditions error and reuse k8s client

[xichengliudui]

What type of PR is this?

/kind bug

What this PR does / why we need it:

fix set node status conditions error, the LastTransitionTime has not been set

Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                          Message
  ----                 ------  -----------------                 ------------------                ------                          -------
  NetworkUnavailable   False   Wed, 15 Oct 2025 10:19:52 +0800   Wed, 15 Oct 2025 10:19:52 +0800   FlannelIsUp                     Flannel is running on this node
  MemoryPressure       False   Fri, 17 Oct 2025 14:06:26 +0800   Fri, 17 Oct 2025 14:06:26 +0800   KubeletHasSufficientMemory      kubelet has sufficient memory available
  DiskPressure         False   Fri, 17 Oct 2025 14:06:26 +0800   Fri, 17 Oct 2025 14:06:26 +0800   KubeletHasNoDiskPressure        kubelet has no disk pressure
  PIDPressure          False   Fri, 17 Oct 2025 14:06:26 +0800   Fri, 17 Oct 2025 14:06:26 +0800   KubeletHasSufficientPID         kubelet has sufficient PID available
  Ready                True    Fri, 17 Oct 2025 14:06:26 +0800   Fri, 17 Oct 2025 14:06:26 +0800   KubeletReady                    kubelet is posting ready status
  Autonomy             True    Fri, 17 Oct 2025 10:49:32 +0800   Sat, 27 Sep 2025 09:04:27 +0800   autonomy enabled successfully   The autonomy is enabled and it works fine

Does this PR introduce a user-facing change?

None

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud