Define Project Syn Tools Versioning Handling and Policy

[tobru]

It's currently not clearly defined how versioning across all the Project Syn tools is handled and how versions are "connected" to each others. It's also not clear where there are compatibility issues, when to raise the version number, and so on.

Therefore we need to define the versioning policy of the overall project so that all Project Syn tools use the same policy. This must also solve the compatibility issues so that the end-user experience gets much better.

Included in this issue is also a research how the documentation could be versioned together with the tooling.

[ccremer]

Dropping a note here.

In a daily sync we decided that if the application in a component is updated to a new major version, the component will also be upgraded to a new major version. Even if the configuration interface for the component doesn't need a change.