chore: On invalid TTL, print the TTL first (#3306)

Before this change we first printed the value, which could be long
resulting in the TTL not appearing in the log due to max line length

If the TTL is invalid, we should print it first to see what value it has

src/server/rdb_load.cc

@@ -647,8 +647,8 @@ void RdbLoaderBase::OpaqueObjLoader::CreateHMap(const LoadTrace* ltrace) {
           int64_t ttl_time = -1;
           string_view ttl_str = ToSV(seg[i + 2].rdb_var);
           if (!absl::SimpleAtoi(ttl_str, &ttl_time)) {
-            LOG(ERROR) << "Can't parse hashmap TTL for " << key << ", val=" << val
-                       << ", ttl=" << ttl_str;
+            LOG(ERROR) << "Can't parse hashmap TTL for " << key << ", ttl='" << ttl_str
+                       << "', val=" << val;
             ec_ = RdbError(errc::rdb_file_corrupted);
             return;
           }