Fix dumb typo in local run number generation

Description

The title says it all... The hour part of the generated local run numbers was not as treated properly.

From the commit message.

Before this commit and since their introduction, the generated local run
numbers were not following the expectations. While not strictly a
problem for their uniqueness, the (approximate) run start time could not
be computed.

Related Issue

How Has This Been Tested?

Trivial change.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

gemsupervisor/src/GEMSupervisor.cpp

@@ -885,7 +885,7 @@ uint64_t gem::supervisor::GEMSupervisor::getNewLocalRunNumber()
 
     uint32_t localRunNumber = 2'000'000'000; // First era
     localRunNumber += ((now.tm_year - 100) * 365 + now.tm_yday - 1) * 100'000; // Epoch on 1 January 2000 00:00:00 UTC
-    localRunNumber += now.tm_hour + 3600 + now.tm_min * 60 + now.tm_sec;
+    localRunNumber += now.tm_hour * 3600 + now.tm_min * 60 + now.tm_sec;
 
     for (;; ++localRunNumber) {
         if (std::filesystem::create_directories(m_outputPath.value_ + "/run" + runNumberToString(localRunNumber, true)))