eth/filters: rangeLogs should error on invalid block range

[vickkkkkyy]

Ran into this while testing a monitoring script - passed fromBlock=100, toBlock=50 by mistake and got back an empty array. Took me way too long to figure out it was just my params being backwards lol.

Turns out updateChainView in the same file already returns errInvalidBlockRange for this case, so just making rangeLogs do the same thing.

[vickkkkkyy]

Greeting! is this good to process? cc @rjl493456442 and @s1na

[s1na]

@vickkkkkyy tests are failing, please fix

--- FAIL: TestFiltersIndexed (3.62s)
    filter_test.go:391: test 12, expected error "", got "invalid block range params"
--- FAIL: TestFiltersHalfIndexed (3.93s)
    filter_test.go:391: test 12, expected error "", got "invalid block range params"
--- FAIL: TestFiltersUnindexed (1.00s)
    filter_test.go:391: test 12, expected error "", got "invalid block range params"
FAIL

[vickkkkkyy]

@vickkkkkyy tests are failing, please fix

--- FAIL: TestFiltersIndexed (3.62s)
    filter_test.go:391: test 12, expected error "", got "invalid block range params"
--- FAIL: TestFiltersHalfIndexed (3.93s)
    filter_test.go:391: test 12, expected error "", got "invalid block range params"
--- FAIL: TestFiltersUnindexed (1.00s)
    filter_test.go:391: test 12, expected error "", got "invalid block range params"
FAIL

fixed

[s1na]

LGTM