Reverts #128640

https://github.com/kubernetes/kubernetes/pull/128640/files#r1965695110

This added a change behavior that regressed the kubelet #130305 @mengqiy @SergeyKanzhelev

The devil is in the details , before

shouldPatchNodeStatus := changed || kl.clock.Since(kl.lastStatusReportTime) >= kl.nodeStatusReportFrequency

but kl.clock.Since(kl.lastStatusReportTime) >= kl.nodeStatusReportFrequency if kl.lastStatusReportTime is time.Time{} or time.Zero is always true time.Since(time.Time{})

and in this patch we changed this meaning , so before it always updated the status after start but now , if there are no changes, it will never update the status

@liggitt is recommending to revert , and backport the revert so we can rework it in the current branch

#130305 (comment)

and I agree with him, after seeing the issue in #130001 and all the indirect dependencies associated to the status update we can not be sure that fix forwarding we don't find a new weird bug, this took @lentzi90 a lot of work to figure it out, who could imagine that the certificate creation was dependong on the node status update

Fixes: #130001

/kind bug
/kind regression

Fixes a 1.32 regression where nodes may fail to report status and renew serving certificates after the kubelet restarts

/assign @dims @liggitt
/sig node