On delete, also attempt to update controller state

In case we missed a previous update.  Add a test to validate that this works
Suggested comment somewhere around here:
// Ensure that the final state of a replication controller is applied before it is deleted. Otherwise, a replication controller could be modified and then deleted (for example, from 3 to 0 replicas), and it would be non-deterministic which of its pods continued to exist.