Create Version scheme independent from Subversion version

[pde-cds]

Because Subversion does not seem to get updates in the near future, but there might be a need to update to newer dependency versions.

We need to create a new version scheme which does not depend on Subversion as main criteria.
@rhuijben Any thoughts on this topic. You might be also the first one to ask were this must be changed

[rhuijben]

I originally folded the Subversion in the first two digits, just for this purpose. The third digit used to be the Subversion revision of the SharpSvn repository, but that got lost when moving to GitHub.

In the native versioning we have UpTo 65535 versions in the third version group, and nuget allows more digit groups, so we have some room to move. Otherwise I think we can move the Subversion minor to the first field. I don't think there will ever be a Subversion 2, that really breaks backwards compatibility. That would just be a new tool.