Improvments for Deployment using Security Level HIGH

Current Situation

When deploying scheduling objects to a Controller using Security Level HIGH, then the same versionId is present in each *.workflow.json file of the export archive file that is created for signing. On import-deploy the versionId will be used from one of the workflows included.

Desired Behavior

If the export archive file does not contain workflows, then the process described above will fail as no versionId can be determined. The versionId is used as the "commitId" for a deployment and has to be available on import-deploy even if no verisoned items are present in the import archive file.

The versionId is stored as an additional property in the meta_inf file with the export archive file in case of exports using the for signing option.

The existing mechanism to traverse *.workflow.json files from the import archive file remains in place as a fallback.