include update_status in default refresh events

[simskij]

Issue

If something alters the state of the kubernetes service patch, there currently is no passive refresh event that could serve as an initiator for self-healing.

Solution

Also observe update_status as a refresh event.

Context

Testing Instructions

1. deploy cos
2. make sure the traefik service is patched
3. kubectl rollout restart sts/controller -n <your-controller-namespace>
4. see traefik service reverting to ClusterIP
5. wait for update_status
6. verify the services is back to being a LoadBalancer

Release Notes

Observe update_status as a refresh event by default.