fix: getEvents queries with not existing block number should be bounded to [0,latest]

[EgeCaner]

Current approach was upon receiving query on getEvents with to_block greater than the height, we were bounding the range to [0, Pending] but Pending block does not have blocknumber and this behavior might be confusing for some user. What they experience is for such queries they are receiving some events for non-existing block and response does not specifies block number for such events since Pending block does not have block number. With this PR, queries with block numbers will be bounded in range [0, latest] and pending block events will be only returned when it is explicity queried with pending or pre_confirmed tag.

Closes #2955

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (0.14.0-beta@42ce4cc). Learn more about missing BASE report.

Additional details and impacted files

@@              Coverage Diff               @@
##             0.14.0-beta    #2963   +/-   ##
==============================================
  Coverage               ?   73.00%           
==============================================
  Files                  ?      284           
  Lines                  ?    32604           
  Branches               ?        0           
==============================================
  Hits                   ?    23803           
  Misses                 ?     7246           
  Partials               ?     1555           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.