chore(test): Fix the unstable spec ForksContainSameUncle caused by block hash collision

[chenyukang]

What problem does this PR solve?

ForksContainSameUncle has the chance of 1/10 to fail in my local machine with error Uncles(DoubleInclusion), after debugging I found the uncle block hash is same with new block hash in node_b.mine(1).

This issue was fixed in 0dc63c2

But it's reverted in the following changes, I believe it is unintentional.

What is changed and how it works?

Make sure the uncle block timestamp is different from the next block timestamp in main fork

What's Changed:

Related changes

• PR to update owner/repo:
• Need to cherry-pick to the release branch

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code ci-runs-only: [ quick_checks,linters ]

Release note

None: Exclude this PR from the release note.