An AuthenticationTokenSecretManager leader won't step down if another RS claims to be a leader

We ran into a situation were a rogue Lily HBase Indexer SEP Consumer sharing the same zookeeper.znode.parent claimed to be AuthenticationTokenSecretManager for an HBase cluster. This situation undesirable since the leader running on the HBase cluster doesn't steps down when the rogue leader registers in the HBase cluster and both will start rolling keys with the same IDs causing authentication errors. Even a reasonable "fix" is to point to a different zookeeper.znode.parent, we should make sure that we step down as leader correctly.