Replicator background task doesn't take conflict resolution into account

From the backtrace provided in the CBSE ticket, the issue happens when resolving conflicts by the replicator. When the app goes into background, the replicator will request for a background task to continue to replicate while the app is in the background until the replicator goes IDLE. However, the conflict resolving process happens in a background queue could continue even after the replicator status is IDLE. As a result, the requested background task could be canceled or stopped while the conflict resolving process is still running, and I guessed that could cause the file protection issue.