Drive: metadata update (other than title) on a remote folder should not be considered as a remote modification

Let's say a folder is locally deleted and one of its properties other than dc:title is updated concurrenlty, then currently the pair state once local and remote states get updated is ('deleted', 'modified'), which leads to the 'remotely_created' state, thus the folder will not be deleted remotely and worse re-created locally.
This can typically happen if an asynchronous listener updates a property on the folder and this update is detected by the client (when fetching the remote change summary) after a period of time during which a local modification has occurded.