MB-9612: handling remote_cluster_info error more gracefully

Today during vb replicator initialization, if remote_cluster_info
fails to grab remote bucket info for any reason, the vb
replicator will crash on a badmatch error and the throttle
will reschedule the next waiting one. This immediate-retry-
after-failure behavior may cause more repeated errors from
remote and vb replicators at source side may crash repeatedly
for nothing.

This commit will make vb replicator consume the error from
remote_cluster_info. If any error returns, the vb replicator
will pause for sometime (default is 30 seconds), and re-query
remote_cluster_info. If the TMP error at remote resolves in
30 seconds, the vb replicator will continue initialization
without crash. If the error persists after 30 seconds, XDCR
will not be able to start as expected.

Change-Id: I39921754887686c0b969b53eb0e4a5764b385145
Merge "MB-9612: handling remote_cluster_info error more gracefully" into for-rackaware