Publish to NPM doesn't add all the Step properties to package.json (missing automationWorkflowFileBasePath in IoT Masterdata)

[Filipecordeiro]

When the envmanager downloads packages from a NPM source it uses the steps defined in package.json file instead of the manifest.xml.
When the cli publishes a (zip) package to an NPM source, it converts it into a tgz and creates a package.json based on the information in the manifest.xml but unfortunately it is not copying every single field of the steps. For example for the IoT Data packages, it's not copying the automationWorkflowFileBasePath . This causes an installation to fail because the masterdata package cannot find the workflows.

Example of the manifest steps of a IoT Data package:

<steps>
    <step
        type="MasterData"
        title="Master Data"
        filePath="MasterData/120_FEC_IoT_OIB.json"
        createInCollection="false"
        automationWorkflowFileBasePath="AutomationWorkFlows"
        targetPlatform="Self" />
</steps>

Example of the package.json steps generated by the Publish:

"steps": [
  {
    "filePath": "MasterData/120_FEC_IoT_OIB.json",
    "order": 0,
    "type": "MasterData",
    "title": "Master Data"
  }
]