Ie26fbd03 added support to rebase with conflicts, but also added setting
the change as WIP when there are conflicts. When setting a change WIP to
true or false, the attention set changes, which added or removed users
unnecessarily during rebase. Also, rebase could change the status (WIP)
of the change even if there are no conflicts (it set to true even if
there are no conflicts).
Fix to ensure to only change to WIP if there are conflicts AND the
change is not WIP yet.
Add tests to make sure attention set and WIP were not changed.
Technically we could add a bunch more tests also for attention set e.g
rebaseWithConflictsDoesNotRemoveFromAttentionSet_changeAlreadyWIP and
rebaseWithConflictsDoesNotRemoveFromAttentionSet_changeNotWIP, and maybe
others. I think it's fine as is though.
Bug: Issue 14046
Change-Id: I77d1311cea6c376708b3ad8a2324091db68a76cf
5af240ed3d