Perforce integration creates bad changelist

Perforce integration creates bad changelist when deleting or renaming a file, then renaming another into its place

Here are the repro steps as provided from the user:

1. Use a project that is synced with P4 and has at least two assets that are already checked in. Have P4 integration set up and an empty pending changelist.
2. There are now 2 different methods to trigger the bug, likely caused by the same issue:
   • A --
     3. Delete one of the assets 
     4. Rename the other asset to the name of the asset you just deleted.
     5. Check it out. 
     6. It will give you a prompt that the asset was writable but not checked out. Click close.
     7. The file you just renamed the second asset to is still marked for deletion. The pending changelist that deletes two assets.

— B —
3. Rename one of the assets.
4. Check it out.
5. Fix redirectors for the folder the assets are in.
6. Notice the pending changelist with the old file marked for deletion and the new file marked for add.
7. Rename the other asset to the previous name of the asset you just renamed
8. Check it out
9) It will give you a prompt that the asset was writable but not checked out. Click close.
10) The file you just renamed the second asset to is still marked for deletion. The pending changelist that successfully renames the first asset, but deletes the second asset

Expected: A pending changelist with the first asset file checked out for edit, the second asset file checked out for deletion, and the new file of the first asset checked out are added to the changelist.

Result: The second asset is deleted from the changelist