feat(swip25): pull syncing optimization

[nugaon]

This SWIP describes a more efficient way to synchronise content between peers in the same neighbourhood by syncing each chunk only once. It removed the maxPOdelta exception for syncing bins from peers below storage depth. Accordingly, bee should not allow shallow receipts on pushing chunks. That should be tackled in a different PR.

Forwarding chunks to the closest address on the network is also required since chunks will be pulled from its closest full nodes.

This is the implementation of SWIP 25 for details check the proposal.

Checklist

• [ ] I have read the coding guide.
• [ ] My change requires a documentation update, and I have done it.
• [ ] I have added tests to cover my changes.
• [ ] I have filled out the description and linked the related issues.

Description

Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):