Don't disconnect peers on fast sync criteria

[LukaszRozmej]

Changes

• Stop disconnecting peers based on fast sync criteria
• This should go after Disconnect Peers based on ForkId validations #5172 in order for us not to have useless peers

Open question:

• Should we still disconnect, but only when we are syncing?

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Should be tested on actual networks

[MarekM25]

Have you checked this code on any node? I wonder how it works in practice. I can imagine that thanks to that code we still drop lots of unuseful peers so it might affect our networking a lot potentially

[MarekM25]

@smartprogrammer93 is right, DropWorstPeer doesn't look like something that should be removed

[LukaszRozmej]

Synced my node on it, looks fine.

[marcindsobczak]

Removed code looks not needed