CLONE - Changing cm:name with REST API /nodes/{nodeId} does not update Primary Path

Problem Description:

Using the REST API to update the cm:name of a folder does not also update the Primary Path associated with the node.  If cm:name is changed using SHARE then the Primary Path is updated.

When the Primary Path is not updated, this can lead to problems with searches.

Reproduction Steps:

1/. Install OOTB ACS v5.2.4.1

2/. Create a new site 'josie-site'

3/. Create a nested folder structure under josie-site: folder1 -> folder2 -> folder3

4/. Add a file 'testfile1' to folder3

5/. Check folder1 properties in the Node Browser (see attached: folder1 properties.png)

6/. Check 'testfile1' properties in the Node Browser (see attached: testfile1 properties.png)

7/. Search for testfile1 in the Node Browser:

+PATH:"app:company_home/st:sites/cm:josie-site/cm:documentLibrary/cm:folder1/cm:folder2/cm:folder3/cm:testfile1"

The file is found.

8/. Using the REST API, change folder name (cm:name) to '1redlof'

http://localhost:8080/alfresco/api/-default-/public/alfresco/versions/1/nodes/0aca470c-fb57-4db5-84b7-55375d237385

{
  "properties":
  {     "cm:name":"1redlof"   }
}

9/. Check '1redlof' properties in the Node Browser (see attached: 1redlof properties.png)

10/. Check 'testfile1' properties in the Node Browser (see attached: testfile1 properties-2.png)

11/. Search for testfile1 in the Node Browser:

+PATH:"app:company_home/st:sites/cm:josie-site/cm:documentLibrary/cm:1redlof/cm:folder2/cm:folder3/cm:testfile1"

The file is not found.

+PATH:"app:company_home/st:sites/cm:josie-site/cm:documentLibrary/cm:folder1/cm:folder2/cm:folder3/cm:testfile1"

The file is found

Observed Behaviour:

When updating the cm:name, the Primary Path is not changed.

Expected Behaviour:

Changing cm:name should also update the Primary Path.

NOTE: This appears similar to MNT-19456.