[bug] InformerController's Retry Logic Doesn't Abandon Retries

[Austin Pond]

The operator.InformerController will attempt retries of erroring watcher calls according to the RetryPolicy, and will abandon previous retries on an object if a newer retry comes into play. However, it does not abandon retries if a new update or delete comes in, which it should, as that retry could now produce unpredictable behavior (and, in the case of a delete, the object no longer exists to execute the retry against).