Add transaction data decoding support

[iuwqyir]

TL;DR

Added transaction data decoding functionality for transactions when a function signature is provided.

What changed?

• Introduced new ABI parsing utilities to handle function signatures
• Added support for decoding transaction input data using parsed ABI
• Created a new DecodedTransaction type that includes the original transaction data along with decoded parameters
• Enhanced transaction handlers to decode transaction data when a function signature is provided

How to test?

1. Make a request to /{chainId}/transactions/{contractAddress}/{signature}
2. Verify that the response includes decoded transaction data with:
   • Function name
   • Function signature
   • Decoded input parameters as key-value pairs
3. Test with various function signatures, including those with complex parameter types (tuples, arrays)
4. Verify that regular transaction endpoints continue to work without decoded data

Why make this change?

To improve transaction data readability by automatically decoding the raw input data into human-readable format when the function signature is known. This makes it easier for users to understand the actual parameters passed in contract interactions without having to manually decode the transaction data.

[iuwqyir]

• decode events #125
• Add transaction data decoding support #124 👈 (View in Graphite)
• do not poll more than the configured amount when filling gaps #123
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[iuwqyir]

Merge activity

• Dec 6, 2:56 PM EST: A user started a stack merge that includes this pull request via Graphite.
• Dec 6, 2:58 PM EST: Graphite rebased this pull request as part of a merge.
• Dec 6, 2:58 PM EST: A user merged this pull request with Graphite.