feat: implement search_transactions_before and search_transactions_after

[caglaryucekaya]

Will close #13499 later.

For now, this PR has an implementation for search_transactions_after. I will add the implementation for search_transactions_before after getting feedback.

[caglaryucekaya]

@mattsse I have some questions. In the issue you wrote that we should enforce a page size limit like 100 blocks. However, according to the documentation the page size argument is not blocks but the number of transactions, so we can put a limit to that.

One problem with my current implementation is that it processes blocks one by one until all the traces are fetched because we don't know in advance in which block we are going to reach the page_size number of transactions. The problem is that since the blocks are not processed in parallel, if the user e.g. request the search beginning from the genesis block and the searched addresses appear far later, the search can take hours.

I will also look into your suggestion to use AccountReader for optimization.