Check for ancient barriers in eth_syncing

[deffrian]

Fixes | Closes | Resolves #

Anything marked as optional that you didn't need to fill in, please remove it from the PR description. Choose one of the keywords above to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666). If there is no issue, remove the line. Remove this note after reading.

Changes:

• If DownloadBodies or DownloadReceipts are enabled eth_syncing will be true until barriers is reached

Types of changes

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

• [ x ] 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

• [ x ] Yes
• No

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

• [ x ] Yes
• No

[LukaszRozmej]

Please fix the build and test scenarios with barriers at 0 as well as subscription

[LukaszRozmej]

Looks good, fix pipeline, test + some minor comment