Incorrect path parsing for custom schema extensions

[cycp]

Describe the bug
Custom schema extensions will be parsed incorrectly. The following example will add bar: "some value" to the path "urn:scim:schemas:extension:foo:1.0".User instead of "urn:scim:schemas:extension:foo:1.0:User".

To Reproduce
Attempt a patch operation with a custom schema extension. e.g.

{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:PatchOp"
  ],
     "Operations":[
       {
         "op":"replace",
         "value": {
            "urn:scim:schemas:extension:foo:1.0:User": {
                bar: "some value",        
            }
         }
       }
     ]
}

Expected behavior
Operations for custom schema extensions should replace the values at the correct path, both when path is defined and not defined in data.Operations.

[chenlevy4]

+1