If two peer have same speed, randomly try the other one.

[asdacap]

Fix #5014

• It was observed in sepolia where during snap sync sometimes nethermind account request timed out on a peer. The peer got sleep as expected, it then try another peer, which also timed out, which then got sleep, then got allocated back to the first peer, then timeout again.
• This should change the peer allocation to try other peer also if it has the same speed.

Changes:

• Add a clause to randomly try other peer if it has the same speed.

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests??

• Yes
• No

Comments about testing , should you have some (optional)

Further comments (optional)

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...