ospack: Ship rngd on all the images, not just minimal

With newer kernels it takes far longer in early boot to get random
numbers (as >= 4.18 kernels ensure good quality entropy is availble
before starting  providing randomness).

Commit 85cc6eba took care of the minimal ospack/images introducing
rng-tools to integrate with hardware random number generators
while jitterentropy-rngd can provide randomness without.

This commit applies the same change to the target, basesdk and sdk
ospacks/images.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

apertis-ospack-basesdk.yaml

@@ -43,6 +43,15 @@ actions:
       - initramfs-tools
       # - apertis-customizations
 
+  # Add rng-tools for devices that have a hardware number generator
+  # Add jitterentropy-rngd for those without
+  # On final production images this can be tuned based on the device
+  - action: apt
+    description: "RNG packages"
+    packages:
+      - rng-tools5
+      - jitterentropy-rngd
+
   - action: apt
     description: "Base packages"
     packages:

apertis-ospack-sdk.yaml

@@ -44,6 +44,15 @@ actions:
       #- apertis-customizations
       - initramfs-tools
 
+  # Add rng-tools for devices that have a hardware number generator
+  # Add jitterentropy-rngd for those without
+  # On final production images this can be tuned based on the device
+  - action: apt
+    description: "RNG packages"
+    packages:
+      - rng-tools5
+      - jitterentropy-rngd
+
   - action: apt
     description: "Base packages"
     packages:

apertis-ospack-target.yaml

@@ -42,6 +42,15 @@ actions:
       # - apertis-customizations
       - initramfs-tools
 
+  # Add rng-tools for devices that have a hardware number generator
+  # Add jitterentropy-rngd for those without
+  # On final production images this can be tuned based on the device
+  - action: apt
+    description: "RNG packages"
+    packages:
+      - rng-tools5
+      - jitterentropy-rngd
+
   - action: apt
     description: "Base packages"
     packages: