Include component name in path for nested modifications

[AntoineGautier]

Related Issue(s)

This addresses #480.

Testing

The parsed template file templates.json now contains adequate modifier keys:

    {
      "modelicaPath": "Buildings.Templates.AirHandlersFans.VAVMultiZone",
      "type": "Buildings.Templates.AirHandlersFans.VAVMultiZone",
      "name": "Multiple-zone VAV",
      "value": "Buildings.Templates.AirHandlersFans.VAVMultiZone",
      "visible": false,
      "modifiers": {
        "Buildings.Templates.AirHandlersFans.VAVMultiZone.nZon.min": { // Correct for modification 'nZon(min=...)'

where it used to be

    {
      "modelicaPath": "Buildings.Templates.AirHandlersFans.VAVMultiZone",
      "type": "Buildings.Templates.AirHandlersFans.VAVMultiZone",
      "name": "Multiple-zone VAV",
      "value": "Buildings.Templates.AirHandlersFans.VAVMultiZone",
      "visible": false,
      "modifiers": {
        "Buildings.Templates.AirHandlersFans.VAVMultiZone.min": { // Incorrect for modification 'nZon(min=...)'

End-to-end tests have been performed by creating the SOO document with the following system options.

AHU

• Separate dampers w/ dp
• Modulating relief w/o fan
• No heating coil
• Freeze stat hardwired to both

Cooling-only box

• 3 sensors = true

The feature branch produces the same document as the main branch.