Load and saving non-workspace vdb fails to retain udf jars and other files

Vdbs that contain either udf libaries or 'other files' are prone to losing these files when edited in Designer.

This only occurs if the vdb is not part of a project, in that its constituent files are not part of the workspace.

When such a vdb is opened by the editor, the archive is extracted to the staging area and the metadata loaded into the in-memory model. The vdb can be edited and saved.

However, the save results in the udf jars and 'other files' not being included in the updated archive.