cr_actions: RenameMergedAction doesn't need to make a new createOp
cr_actions: RenameMergedAction doesn't need to make a new createOp

There will always be a createOp in the unmerged branch already since
that's the only way the merged branch can be considered in conflict.

Issue: KBFS-571

keybase/client,keybase/client,keybase/client,keybase/kbfs,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/kbfs,keybase/client,keybase/client,keybase/kbfs,keybase/client,keybase/kbfs