Improve logging during sync

[StefanBratanov]

PR Description

Fixed Issue(s)

fixes #9220

Documentation

• I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

[gfukushima]

lgtm, with a question on the return of SyncManager::getSyncStatus

[gfukushima]

the const 1 here might be a bit misleading if it comes out in one of the logs, should we print the total amount of peers instead even though they might not all have the same target?

[tbenr]

let's put this LOG back to debug too

teku/beacon/sync/src/main/java/tech/pegasys/teku/beacon/sync/forward/multipeer/MultipeerCommonAncestorFinder.java

Lines 71 to 72 in 3d0dd71

	return findCommonAncestor(latestFinalizedSlot, targetChain)
	.thenPeek(ancestor -> LOG.info("Found common ancestor at slot {}", ancestor));

[tbenr]

I added an experimental change to the PR, adding more info taken from the BatchSync.
It is not good in the current form but we can play with it until we find the final form.

[StefanBratanov]

Hoodi syncing