Change kuksa-client version handling

Does the following:

- For Docker copy whole repo so we get the expected version from tag
  (previously always 0.1.6)
- Using 0.1.6 as default version does not make sense,
  0.0.0 works better to show that version lookup failed
- Tag pattern seems to be difficult to get correct, it always complain
  and seems to have no effect
- Aligning grpcio-tools version with what is defined in setup.cfg

The reason is that all docker build on master
previously got v0.1.6 except possible if that specific version was tagged, which
gives odd behavior if downloading kuksa-client:master

Author: erikbosch

kuksa-client/Dockerfile

@@ -10,11 +10,10 @@
 
 FROM python:3.10-alpine as build
 RUN apk update && apk add git alpine-sdk linux-headers
-COPY kuksa-client /kuksa.val/kuksa-client/
-COPY kuksa_certificates /kuksa.val/kuksa_certificates/
-COPY proto/kuksa/val/v1/*.proto /kuksa.val/kuksa-client/kuksa/val/v1/
-WORKDIR /kuksa.val/kuksa-client
 RUN pip install --upgrade pip build
+# We must copy the whole repository otherwise version lookup by tag would not work
+COPY . /kuksa.val/
+WORKDIR /kuksa.val/kuksa-client
 RUN rm -rf dist
 RUN python3 -m build
 RUN mkdir /kuksa-client

kuksa-client/pyproject.toml

@@ -1,15 +1,15 @@
 [build-system]
 requires = [
-    "grpcio-tools>=1.46.0",
+    "grpcio-tools>=1.54.2",
     "setuptools>=42",
     "setuptools-git-versioning",
     "wheel",
 ]
 build-backend = "setuptools.build_meta"
 
 [tool.setuptools-git-versioning]
-starting_version = "0.1.6"
-tag_filter = "[0-9]+.[0-9]+.[0-9]+"
+# Starting version is just a dummy value that never shall be used in CI
+starting_version = "0.0.0"
 
 [tool.pylint.design]
 max-args = 8