fix: use the peer with the highest score when syncing

[darrenvechain]

Description

This changes the behaviour when choosing a peer to sync with. It picks the peer with the highest score, rather than the peer with a higher score

Type of change

Please delete options that are not relevant.

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• [X] - Unit tests

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] New and existing E2E tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have not added any vulnerable dependencies to my code

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 80.00000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 61.40%. Comparing base (0489d6a) to head (cdc177b). Report is 1 commits behind head on master.

Files	Patch %	Lines
comm/communicator.go	0.00%	2 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #735 +/- ## ========================================== + Coverage 61.37% 61.40% +0.02% ========================================== Files 194 194 Lines 18223 18228 +5 ========================================== + Hits 11184 11192 +8 + Misses 5958 5955 -3 Partials 1081 1081 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.