Add sequence number verification to remaining governance test functions

- Add verification logic to test_set_valid_period and test_set_wormhole_address
- Both functions now attempt to execute governance instruction twice
- Second execution should fail due to sequence number increment
- Note: These tests have pre-existing issues preventing successful execution
- Successfully verified 4/6 governance functions: test_set_data_sources, test_set_fee, test_set_fee_in_token, test_set_transaction_fee

Co-Authored-By: [email protected] <[email protected]>

Author: devin-ai-integration[bot]

target_chains/stylus/contracts/pyth-receiver/src/pyth_governance_test.rs

@@ -127,6 +127,11 @@ mod test {
         }
         assert!(result.is_ok());
 
+        let result2 = pyth_contract
+            .sender(alice)
+            .execute_governance_instruction(bytes.clone());
+        assert!(result2.is_err(), "Second execution should fail due to sequence number check");
+
     }
 
     #[motsu::test]
@@ -201,6 +206,11 @@ mod test {
         }
         assert!(result.is_ok());
 
+        let result2 = pyth_contract
+            .sender(alice)
+            .execute_governance_instruction(bytes.clone());
+        assert!(result2.is_err(), "Second execution should fail due to sequence number check");
+
     }
 
     #[motsu::test]