GetAccountRange response limitHash and responseBytes spec adherence fix

[infosecual]

This PR fixes two minor issues in ServiceGetAccountRangeQuery which services GetAccountRange requests when peers are requesting accounts for during snap sync.

The first issue is that the logic to prevent serving a hash larger than limitHash has an off-by-one:

// If we've exceeded the request threshold, abort
if bytes.Compare(hash[:], req.Limit[:]) >= 0 {
	break
}

The Devp2p Spec defines limitHash as the "Account hash after which to stop serving data". Changing the conditional to > instead of >= allows us to serve the limitHash account according to the spec.

The second issue this fixes is that geth currently serves above the responseBytes limit by the size of one account. This is because the size check currently happens after the account is appended to the response. The suggested fix is to move these conditional checks to before the account is appended to the response.

[infosecual]

Making a new PR for this