f also test in fuzzing

Author: TheBlueMatt

lightning/src/routing/router.rs

@@ -206,7 +206,7 @@ struct PathBuildingHop {
 	/// decrease as well. Thus, we have to explicitly track which nodes have been processed and
 	/// avoid processing them again.
 	was_processed: bool,
-	#[cfg(test)]
+	#[cfg(any(test, feature = "fuzztarget"))]
 	// In tests, we apply further sanity checks on cases where we skip nodes we already processed
 	// to ensure it is specifically in cases where the fee has gone down because of a decrease in
 	// value_contribution_msat, which requires tracking it here. See comments below where it is
@@ -628,7 +628,7 @@ pub fn get_route<L: Deref>(our_node_id: &PublicKey, network: &NetworkGraph, paye
 								htlc_minimum_msat: $directional_info.htlc_minimum_msat,
 								path_htlc_minimum_msat,
 								was_processed: false,
-								#[cfg(test)]
+								#[cfg(any(test, feature = "fuzztarget"))]
 								value_contribution_msat,
 							}
 						});
@@ -721,12 +721,12 @@ pub fn get_route<L: Deref>(our_node_id: &PublicKey, network: &NetworkGraph, paye
 								old_entry.channel_fees = $directional_info.fees;
 								old_entry.htlc_minimum_msat = $directional_info.htlc_minimum_msat;
 								old_entry.path_htlc_minimum_msat = path_htlc_minimum_msat;
-								#[cfg(test)]
+								#[cfg(any(test, feature = "fuzztarget"))]
 								{
 									old_entry.value_contribution_msat = value_contribution_msat;
 								}
 							} else if old_entry.was_processed && new_cost < old_cost {
-								#[cfg(test)]
+								#[cfg(any(test, feature = "fuzztarget"))]
 								{
 									// If we're skipping processing a node which was previously
 									// processed even though we found another path to it with a