Bucket manifest should be reconciled as part of BucketEventsListener recovery

If a KV collection is dropped while the analytics service is down, or is in the process of a recovery for other reason (e.g. NOT_MY_VBUCKET), Analytics can get into a recovery loop based on race condition with the bucket manifest monitor. If the bucket manifest monitor realizes the manifest update and processes it prior to recovery finishing, it will not be handled and the ingestion will fail due to the collection id not being valid. This will trigger another recovery which will repeat the cycle.

Manually reconnecting the applicable link(s) will rectify the issue, but it can recur should a KV collection be dropped again in the future.