[AA] optimize bundler calls for eth_getUserOperationReceipt and eth_getUserOperationByHash

[souradeep-das]

Issue Type

[ ] bug report
[ ] feature request
[X] optimization

Current Behavior

eth_getUserOperationReceipt and eth_getUserOperationByHash endpoints on the bundler take an additional optional parameter that users can use to specify block ranges. However the user may not be aware of the exact block ranges.

Suggested Fix

Store the event logs in a db, and make the bundler query events from the db
Other solution is to use a subgraph, if it is effective
(There may be other solutions)

[InoMurko]

However the user may not be aware of the exact block ranges.

• block ranges the underlying network allows
• block ranges in which his hash IS

whether this is OK for devs for wallets, we don't really know. so... we shall see what the solution is.