Introduce BookieClusterManager and Improve BookieListener

**FEATURE REQUEST**

1. Please describe the feature you are requesting.

- introduce BookieClusterManager class for managing the available/readonly/registered bookies in a centralized place (before that it was spread across different classes)
- improve BookieListener for listening on the topology changes. so the caller of listeners don't have to do this one-time notify actions.

2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

*blocker*

It is a basic change for sub-sequent changes that twitter did on auto-recovery.

3. Provide any additional detail on your proposed use case for this feature.

this change is contributed by @yzang