Backfill request handler's cooldown mechanism is flawed such that it could cause the run() routine to run the persist case when there is no operations to persist.

This can lead to the handler stuck forever waiting for an operation that will never come, and all backfill operations will be unresponsive... such as handling VB done events, or raising future backfills, etc

A typical symptom would be a backfill pipeline that hangs and doesn't go away (potentially with changes_left staying at 0)

The stack trace would show a bunch of go-routines doing HandleVBTaskDone(), (each one per VB), and one go routine stuck at this location:

https://github.com/couchbase/goxdcr/blob/26d8add3a1c760f1c0c99569a4582e7b7c09c689/backfill_manager/backfill_request_handler.go#L296