getLogs should raise pruned history error for block number 0

[s1na]

When querying logs in a pruned node:

> eth.getLogs({ fromBlock: '0x0', toBlock: 'latest' })
Error: failed to get logs for block #0 (0xd4e567..cb8fa3)
        at web3.js:6386:9(39)
        at send (web3.js:5115:62(29))
        at <eval>:1:12(7)

> eth.getLogs({ fromBlock: '0x1', toBlock: 'latest' })
Error: pruned history unavailable
        at web3.js:6386:9(39)
        at send (web3.js:5115:62(29))
        at <eval>:1:12(7)

It means getLogs somehow sees block 0 as special and doesn't do the pruned history check properly on it. I guess it was because 0 was the special block number for the "earliest" tag.

[lunargon]

@s1na I see in this https://github.com/ethereum/go-ethereum/blob/master/eth/filters/api.go#L362:

		if begin > 0 && begin < int64(api.events.backend.HistoryPruningCutoff()) {
			return nil, &history.PrunedHistoryError{}
		}

Change this to begin >= 0 I think this will solved. When block input is 0 can return error:pruned history unavailable

I have PR for this fix.

[s1na]

Fixed via #31941.