Update comments around an old bug workaround

[danwinship]

What this PR does / why we need it:

Updates some comments in the code to refer to a k8s issue rather than a docker issue, with more clarity about when the workaround can be removed.

I didn't bother updating the Event text because nobody has complained about it so far (meaning maybe nobody ever actually hits this bug any more?) and anyway, the original docker bug describes the workaround ("restart docker") while the new k8s bug doesn't...

Which issue(s) this PR is related to:

#134108

Does this PR introduce a user-facing change?

NONE

/kind cleanup
/sig network
/area kube-proxy

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cmd/kube-proxy/OWNERS [danwinship]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[danwinship]

/retest-required