Support for auxiliary files

[iadonkey]

Upload files and let the user specify to destination target. This can be used to

• upload library specific templates
• Device description files
• etc

To handle this use case we archive all files and upload the archive instead of a library file and add a designates files section to the config

[mark-lazarides]

Agree with @iadonkey suggestion, particularly for EDS files. It would be good if those were versioned.

We also often use json docs to store object configurations, and/or recipe type information. It would be great to have a way to store those for developer PC. Even better if we could do that for production, but I assume that makes demands on the dev -> plc connection.

[iadonkey]

While it doesn't really effect the implementation of the feature to include arbitrary files in a package and assign a target location to them, I do have legal concern if users start to distribute files where they are not the copyright holder to. Guess we have to read some terms and conditions and check with some vendors about that.

I create a seperate issue for deploying files to targets