What was expected?:
If a user deletes an asset file, and then pulls a collab update that contains a change where another user recased the delete file's name, the file should be recreated local with the new recasing, but otherwise the file should remain the same as if never deleted.

What actually happened?:
The file is recreated with the correct name casing, but the editor refuses to reissue the old GUID to it because, according to the messaging, the old GUID is reserved for the file with the old file name casing, and instead issues a new GUID. This potentially breaks any references based on the asset's GUID, resulting in potential loss of work.

How can it be reproduced?:
1) User 1 renames a file from "MyScript.cs" to myScript.cs".
2) User 2 deletes the "MyScript.cs" file from their local project.
3) User 1 publishes their recase change.
4) User 2 pulls the update.
5) User 2 should observe at this point the GUID assignment warning message in the editor console.

Discovered on the 2017.2.0f1 RC1 build.