Fix tracing of the chained incoming moves in the tree conflict resolver.
We only need to take the last-changed revision of the deleted node into account while mapping a delete+copy pair to a move, instead of also doing this when chaining moves.
* subversion/libsvn_client/conflicts.c (check_move_ancestry): Accept new argument that makes the last-changed revision check conditional. (find_moves_in_revision): Update the calling sites of check_move_ancestry(). Check the last-changed revision when resolving moves within a single revision, and don't do that when gluing moves that happened in different revisions.
* subversion/tests/libsvn_client/conflicts-test.c (test_funcs): The test_merge_incoming_chained_move_local_edit() test now passes.