[EPIC] Custom API Support for Explorers

[Nana-EC]

Problem

Many web3 products rely on cuistom APIs on the EVM block explorer (e.g. Etherscan, BlockScouts, etc), however, our MNE is split up as a clients and a backend that's HAPI focused.
Therefore there's no EVM focused REST API's to support some of these expected APIs

Etherscan required APIs endpoints:

1. https://docs.etherscan.io/api-endpoints/blocks#get-block-and-uncle-rewards-by-blockno (module=block, action=getblockreward)
2. https://docs.etherscan.io/api-endpoints/accounts#get-a-list-of-erc721-token-transfer-events-by-address (module=account, action=tokennfttx)
3. https://docs.etherscan.io/api-endpoints/accounts#get-a-list-of-erc1155-token-transfer-events-by-address (module=account, action=token1155tx)

Blockscout RPC API endpoints:

1. https://docs.blockscout.com/devs/apis/rpc/block#get-block-reward-by-block-number (module=block, action=getblockreward)
2. https://docs.blockscout.com/devs/apis/rpc/account#get-token-transfer-events-by-address (module=account, action=tokentx)
3. https://docs.blockscout.com/devs/apis/rpc/account#get-list-of-tokens-owned-by-address (module=account, action=tokenlist)

Solution

Add custom REST API support to the relay which will allow the MNE to pass through queries and responses to satisfy community expectations on these APIs

Block Explorer Supporting Custom API Tasks

Preview Give feedback

1. Research Etherscan & BlockScout APIs to confirm priority list offering #3324
   1 of 2
   enhancement +1
   
2. Create design doc to support REST API #3340
   design +1
   

Alternatives

No response