use 3.4.0-M1 milestone as appVersion instead of "nightly"

Signed-off-by: Thomas Jäckle <thomas.jaeckle@beyonnex.io>

deployment/helm/ditto/Chart.yaml

@@ -16,8 +16,8 @@ description: |
   A digital twin is a virtual, cloud based, representation of his real world counterpart
   (real world “Things”, e.g. devices like sensors, smart heating, connected cars, smart grids, EV charging stations etc).
 type: application
-version: 3.3.10  # chart version is effectively set by release-job
-appVersion: nightly
+version: 3.4.0  # chart version is effectively set by release-job
+appVersion: 3.4.0-M1
 keywords:
   - iot-chart
   - digital-twin

deployment/helm/ditto/values.yaml

@@ -1238,7 +1238,13 @@ connectivity:
       timerThreshold: 100ms
       # creditsPerBatch configures how many "cleanup credits" should be generated per "interval" as long as the
       creditsPerBatch: 5
-    # persistence holds configuration regarding (pekko) persistence of connections (event journal and snapshots)
+      # deleteFinalDeletedSnapshot configures whether for a deleted entity, the final snapshot (containing the
+      #  "deleted" information) should be deleted or not.
+      #  If the final snapshot is not deleted, re-creating the entity will cause that the recreated entity starts with
+      #  a revision number 1 higher than the previously deleted entity. If the final snapshot is deleted as well,
+      #  recreation of an entity with the same ID will lead to revisionNumber=1 after its recreation.
+      deleteFinalDeletedSnapshot: true
+    # persistence holds configuration regarding (akka) persistence of connections (event journal and snapshots)
     persistence:
       # keep closed, inactive connections for that amount of time in memory when no other use did happen:
       activityCheckInterval: 45m