Account 'status' (and 'status_changed_at'?) need to replicate

[Tim Burke]

Currently, 'status' and 'status_changed_at' don't replicate in any meaningful way. As a result, you can get in a weird state where a client gets back a 204 when deleting an account but only 2/3 replicas think an account should be deleted.

Assuming there's data in the account, there are a few different ill effects:

* GETs come back 204 (because while that third replica gets a delete_timestamp, it still has data),
* container PUTs come back 404 (because of the account update response received inline with the container-server request) *but still create a container DBs*, and
* the reaper never cleans up the last 1/3 of containers (since it divides work across the three replicas).