sample-image-production: Write os-release before cleaning up root

The /etc/os-release file is edited in the chroot environment (chroot: true),
but that chroot env cannot be accessed after the "Reset rootfs before
deploying OSTree" step (chroot is failing because /etc/resolv.conf is
missing)

It also makes sense to edit /etc/os-release before running the "OSTree
commit" step to include the correct /etc/os-release in the ostree commit.
So the editing of /etc/os-release ("Customize image version metadata"
step) is moved right before that.

Fixes: apertis-issues#151
Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

sample-image-production.yaml

@@ -38,6 +38,12 @@ actions:
     packages:
       - python3
 
+  # Run scripts to customize your rootfs
+  - action: run
+    description: "Customize image version metadata"
+    chroot: true
+    script: scripts/setup_image_version.sh {{ $osname }} {{ $suite }} '{{ $timestamp }}' mycompany {{ $type }}
+
   # Adapt and commit OSTree based on rootfs created during previous action
   - action: recipe
     description: OSTree commit for {{ $suite }} {{ $type }} {{ $architecture }}