feat: new bridge history apis

[colinlyguo]

Purpose or design rationale of this PR

1. Supported Features:
   1. Get transactions:
      1. By address:
         1. pagination: page, pagesize.
         2. types: all txs, L2 withdrawals, unclaimed L2 withdrawals.
      2. By transaction hash.
   2. Deposit/Withdraw transaction status (terminal statuses: relayed, failed relayed, dropped):
      1. Sent (emit SentMessage event).
      2. Sent tx reverted: https://etherscan.io/tx/0xc6175136e31e01970efe5255087b6d370bec70c2b3ba21d6201ee78422e5c25f
      3. Relayed (emit RelayedMessage event).
      4. Failed Relayed (emit FailedRelayedMessage event): https://sepolia.scrollscan.com/tx/0x7323a7ba29492cb47d92206411be99b27896f2823cee0633a596b646b73f1b5b
      5. Relayed transaction reverted (only for L2 withdrawals): https://sepolia.scrollscan.com/tx/0x7323a7ba29492cb47d92206411be99b27896f2823cee0633a596b646b73f1b5b
      6. Skipped: replayMessage or dropMessage.
      7. Dropped: done, user has got the refund.
2. APIs:
   1. Get:
      1. /txs?address=0x0&page_size=10&page=1
      2. /l2/withdrawals?address=0x0&page_size=10&page=1
      3. /l2/unclaimed/withdrawals?address=0x0&page_size=10&page=1
   2. Post:
      1. /txsbyhashes

A more detailed doc: https://www.notion.so/scrollzkp/Bridge-History-APIs-ac136e1ac51e4292a66a1153a79d79bb

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• feat: A new feature

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

• Yes

Breaking change label

Does this PR have the breaking-change label?

• Yes