fix: revert timestamp change

In practice, this situation is unlikely to happen, since the timestamp
is set before mining begins. Setting it to the parent timestamp + 1
causes problems in some tests that rely on quickly producing blocks.

Author: obycode

stackslib/src/chainstate/nakamoto/mod.rs

@@ -944,7 +944,7 @@ impl NakamotoBlockHeader {
             parent_block_id,
             tx_merkle_root: Sha512Trunc256Sum([0u8; 32]),
             state_index_root: TrieHash([0u8; 32]),
-            timestamp: std::cmp::max(parent_timestamp.saturating_add(1), get_epoch_time_secs()),
+            timestamp: std::cmp::max(parent_timestamp, get_epoch_time_secs()),
             miner_signature: MessageSignature::empty(),
             signer_signature: vec![],
             pox_treatment: BitVec::ones(bitvec_len)