Versioning and dependency

[Roman M. Yagodin]

DNN use ##.##.## numbering scheme for versioning, and this is also used by DNN Forge and extension feed. Translation packages in the project currently use corresponding extension version + release number ##.##.##-#, which is incompatible with rest of DNN infrastructure.

This can be changed by adding separate semantic versioning for translation packages and by utilizing dependency nodes in the package manifests.

[Roman M. Yagodin]

Typo in commit - fixed #11 instead of #10!

Current DNN dependency implementation won't allow to specify required extension version, only package name. So, targeted extension version provided in the language pack description. Also added core version dependency.