feat(rpc): implement EthGetTransactionByBlockNumberAndIndex

[virajbhartiya]

Summary of changes

Changes introduced in this pull request:

implement EthGetTransactionByBlockNumberAndIndex

Reference issue to close (if applicable)

Closes #5020

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

[elmattic]

You have some CI error:

| Filecoin.EthGetTransactionByBlockNumberAndIndex (5) | Rejected("index 0 out of range: tipset contains 0 messages")                                  | Rejected("failed to get transaction at index 0: index 0 out of range: tipset contains 0 messages")

The failure is likely due to this identity test using the policy PolicyOnRejected::PassWithIdenticalError and in this case error strings do not match.

[elmattic]

Lotus method implementation is accepting values like "latest", "pending", etc? (see filecoin-project/lotus#12618 (comment))

What about us?

[elmattic]

@virajbhartiya can you put the PR back to draft and only turn it to RFR when CI is ✅? Thanks!

In general, no green checkmark => no review.

[elmattic]

https://www.quicknode.com/docs/ethereum/eth_getTransactionByBlockNumberAndIndex

According to the specification, the method accepts only a string in hexadecimal format or tags for the block number. We can also support this by using a type like:

enum BlockNumberOrTag {
    BlockNumber(EthInt64),
    PredefinedBlock(Predefined),
}

Then we can create a conversion function to build a BlockNumberOrHash from this type and pass it to the tipset_by_block_number_or_hash function. What do you think?

Of course, we can choose to diverge from the Ethereum specification (and to what is implemented in Lotus), but this would complicate our efforts to align with a common OpenRPC standard.

See filecoin-project/FIPs#1027.

edit: Actually, we already have similar type implemented, it's calledBlockNumberOrPredefined.

[hanabi1224]

I believe this needs to be moved to under Forest unreleased section