bookie appears in the bookie list after the recover command deletes its cookie

***To Reproduce***

Steps to reproduce the behavior:

1. switch a bookie to read-only `curl -s -X PUT -H "Content-Type: application/json" -d '{"readOnly":true}' :8000/api/v1/bookie/state/readonly`
2. `bin/bookkeeper shell recover -f -d `
3. check that recover succeeded and that the cookie is gone from ZK
4. `curl -s /api/v1/bookie/list_bookie_info` - see that bookie whose cookie is deleted still shows up in the cluster

***Expected behavior***

bookies should not show up in the cluster info after its cookie is deleted by recover command, as if it was decomm'ed