Introduce semantic versioning of the project

[dk1844]

Background

Currently, the project is not version as a whole (clientLibrary is). Let's extend the versioning to the whole project.
Ideally, these tags should then be used for particular docker image builds.

Proposed Solution [Optional]

Solution Ideas:

1. Tag based versioning
2. Version recorded in SBT files
3. Both?

[dk1844]

Current state: we tag the commit in master by a final tag denoting the release. This can be then acted upon with other deployment actions (e.g. Absa-group internal for LS deployment).

There is no public docker-build process to be tagged otherwise, just the client lib is actually released.