REST api does not update the primary path on new version upload

[Description]

Uploading a new version via REST api does not update the primary path of the document.

[Steps to reproduce]

• Install alfresco 5.2.7.5 using the installer

• Start alfresco

• Login as the admin user to share

• Create a site

• Create/upload a text document

• Take note of the node reference

• In the node browser check the node's primary path

• Execute the curl command below to update the text file, note the name change

  [Expected Behaviour]

New version of the document is created and the primary path is updated to the new name of the document

[Observed Behaviour]

New version of the document is created, the primary path of the document remains the same as the original document

[Analysis to date]

Using share's "upload new version" action it updates the document and its primary path. This is the same behavior in alfresco 6.2.2. This issue is causing users to not find the document by path after it's updated. The customer needs a fix for preventing the issue and a fix to cleanup bad data.