fix: nested additional props cause data corruption

[VinzSpring]

Fixed invalid path composition that causes nested additional properties to have invalid values.

An example that previously wouldn't have worked:

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "SomeNestedConfig": {
      "type": "object",
      "default": {},
      "properties": {
        "CsvImportDirectory": {
          "type": ["string", "null"],
          "default": "import"
        },
        "KeyToValueMapping": {
          "type": "object",
          "patternProperties": {
            ".*": {
              "type": "string",
              "title": "Key"
            }
          },
          "additionalProperties": {
            "type": "string",
            "title": "Value"
          },
          "default": {}

        }
      },
      "required": ["CsvImportDirectory", "KeyToValueMapping"],
      "additionalProperties": true
    }
  },

  "required": [
    "SomeNestedConfig"
  ],
  "additionalProperties": true
}

Now it produces valid output.

[CLAassistant]

All committers have signed the CLA.

[netlify]

❌ Deploy Preview for jsonforms-vuetify-renderers failed.

Name	Link
🔨 Latest commit	991855b
🔍 Latest deploy log	https://app.netlify.com/sites/jsonforms-vuetify-renderers/deploys/679ce3f2671d060008b73c9f

[Yekt]

We stumbled across issues when trying to use "additionalProperties" in nested objects.
This fix resovled those problems.