fix(repo): Migrating away from using the cursor field for ordering + pagination

[petertonysmith94]

Summary

• Migrating away from using the cursor field for ordering + pagination

Understanding of the pagination

block_height

       0001
       0002   <---
       0003
       0004

WHERE
 (block_height > 0002)

---

block_height    transaction_index

       0001                    0
       0001                    1   <---
       0001                    2
       0001                    3


WHERE
 (block_height = 0001 AND transaction_index > 1) OR
 (block_height > 0001)

---

block_height    transaction_index     receipt_index

       0001                    0                 0
       0001                    0                 1     <---
       0001                    0                 2     
       0001                    1                 0
       0001                    2                 0
       0001                    3                 0


WHERE (
 (block_height = 0001 AND transaction_index = 0 AND receipt_index > 1) OR
 (block_height = 0001 AND transaction_index > 0) OR
 (block_height > 0001)
)

[luizstacio]

Can we remove the prefix here? I believe some places use it to create pagination over join query. Like predicates endpoint

[petertonysmith94]

I had mitigated this by putting the join_prefix within the cursor_fields like this.

However, I believe it's better to have for consistency (63ec002)

[petertonysmith94]

@luizstacio do we want to merge this one?