Write regression test for the hardware clock not being saved

That is, check that #9364 (closed) remains fixed, e.g.:

--- a/features/time_syncing.feature
+++ b/features/time_syncing.feature
@@ -32,6 +32,12 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect

+  Scenario: The system time is not synced to the hardware clock
+    When I bump the system time with "+1 day"
+    And I warm reboot the computer
+    And the computer reboots Tails
+    Then the hardware clock is still the same as the host's time
+
 #  Scenario: Clock vs Tor consensus' valid-{after,until} etc.

   Scenario: Create a new snapshot to the same state (w.r.t. Sikuli steps) as the Background except we're now in bridge mode

Tip: hwclock -r can be used to query the hardware clock from within Tails in the the hardware clock is still the same as the host's time step (bonus points for a better name that doesn’t refer to the “host”). Then it should be compared to the host’s clock +/- some seconds.

Feature Branch: kytv:test/9557-hwclock

Parent Task: #8543 (closed)

Related issues

• Related to #9364 (closed)

Original created by @anonym on 9557 (Redmine)