Improve fetch_historic_logs_stream logic

[SozinM]

I found a small problem in from/to intervals during fetch_historic_logs_stream. To determine the next block in case when we had any logs returned in this range we are taking the block number of the last block. This causes the following problem: we are ignoring the fact that we are already processed some blocks at the end of the range (if they were empty). Example: Case 1 Range 0-100 returned only one log with block number 50 The current implementation will query the next batch with block range 50-... Case 2 Range 0-100 returned no logs The current implementation will query the next batch with block range 100-...