Correct DNSSEC proof validity time gap applied to header time

We intended to apply DNSSEC proof validity tests to constrain them
to within two hours of the latest block header time, but the code
landed with a two minute gap instead.

Given DNSSEC proof validity is usually many hours and grace periods
are used to ensure records close to expiry aren't used, this is
somewhat unlikely to have bitten anyone.

Author: TheBlueMatt

lightning/src/onion_message/dns_resolution.rs

@@ -637,7 +637,7 @@ impl OMNameResolver {
 				// complicated).
 				// Thus, we have to let the proof times be rather fuzzy.
 				let max_time_offset =
-					if cfg!(all(feature = "std", not(fuzzing))) { 0 } else { 60 * 2 };
+					if cfg!(all(feature = "std", not(fuzzing))) { 0 } else { 60 * 60 * 2 };
 				if validated_rrs.valid_from > time + max_time_offset {
 					return None;
 				}