zamba uses git to manage its version.

This closes issue #20.

We will create dedicated branches and use merge commits on master.
Squashing should only done when changes work on the same feature.

This tag also tries to use `git shortlog --no-merges prior..HEAD` to
summarize the changes:

Thomas (7):
      reused queries should tell their usage pattern to sqlite3--prepare
      fix: synchronized the log output of db-changes to the actual sql in use.
      fix: leaked change from master reverted
      use git tags as the version to propagate
      updated README

First release which we assume to be stable enough to refer to.

Prior behaviour/changelog described from the README:

|- Version -|- Functionality -|
|-----------|-----------------|
| 0.2.1 | initial push to remote |
| 0.3.5 | working gambit-C language server |
| 0.4.0-a | internal functionality was rewritten: json -> alist. |
| 0.5.0 | workspaceFolders, utf-8 support, tcp/ip-communication, tree-sitter-parsing and $/cancelRequest functionality added; hardening |
| 0.6.0 | hover functionality now works with tree-sitter |
| 0.7.0 | completion functionality now works with tree-sitter |
| 0.7.1 | let the user recomplete completions |
| 0.7.2 | change behaviour of declaration and hover (and this one extended) functionality. |
| 0.8.0 | implemented references functionality, new json parser, smaller language ABI, python support added |
| 0.8.1 | improved handling on stdio. Added scheme support. loading bindings of tree-sitter-grammars put into zamba itself. |
| 0.8.2 | introduced the first most essential tests to zamba. new didChange-sync |
| 0.8.3 | new logging format. |
| 0.8.4 | zamba gives feedback on the command line. |
| 0.9.0 | zamba uses diagnostics. |
| 0.9.1 | hover does now pretty-printing. |

Due to unfamiliarity, this may still be tracked within the README.
Undecided yet.

Versions can be managed with git tags.

This has the advantage to refer to the actual commit the user uses
within the version string.
Additionally releases are easier to manage.
One could generate changelogs in the future.
But mainly I just learned this option and want to improve my project
managing workflow.