Allow a failed changelog write in movePrimary's cleanupOnError to silently fail.

The given contract for changelog writes is that these writes are "best-effort," implying that we should not assert on their success. This case in particular is problematic because it's inside a scopedGuard. When an exception is not caught from inside a scopedGuard, it causes std::terminate to be called.

This ticket is to simply change the call from logChangeChecked to logChange, and then remove the uassertStatusOK.