feat: allowed ERC registry indexing tool to target localnet

[quiet-node]

Description:
Contract call APIs interact with the Mirror Node Web3Module, but the local network does not automatically forward these requests. As a result, the indexing tool must manually redirect contract call requests to the Web3Module endpoint.

To address this, this PR introduces the MIRROR_NODE_URL_WEB3 configuration. This addition enables the ERC registry indexing tool to seamlessly execute contract call APIs against the Web3Module, ensuring effective targeting of the local network.

Related issue(s):

Fixes #1070

Notes for reviewer:
This PR builds upon the changes introduced in PR #1064. As a result, many updates from PR #1064 are reflected here.

It is recommended to review PR #1064 before proceeding with this one.

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[github-actions]

Test Results

 16 files  ± 0   83 suites  +1   12m 23s ⏱️ + 2m 8s
294 tests +17  288 ✅ +19  6 💤 ±0  0 ❌  - 2 
303 runs  +15  296 ✅ +17  7 💤 ±0  0 ❌  - 2 

Results for commit f0cc24d. ± Comparison against base commit af82723.

This pull request removes 1 and adds 18 tests. Note that renamed tests count towards both.

"before each" hook for "should be able to update fixed fee in HBARs for NFT" ‑ TokenManagmentContract Test Suite Update fees "before each" hook for "should be able to update fixed fee in HBARs for NFT"

should be able to update fixed HTS fee and royalty fee in NFT ‑ TokenManagmentContract Test Suite Update fees should be able to update fixed HTS fee and royalty fee in NFT
should be able to update fixed HTS fee for NFT ‑ TokenManagmentContract Test Suite Update fees should be able to update fixed HTS fee for NFT
should be able to update fixed fee in HBARs for NFT ‑ TokenManagmentContract Test Suite Update fees should be able to update fixed fee in HBARs for NFT
should fail for updateFungibleTokenCustomFees when token is not associated to fee collector ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail for updateFungibleTokenCustomFees when token is not associated to fee collector
should fail for updateNonFungibleTokenCustomFees when token is not associated to fee collector ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail for updateNonFungibleTokenCustomFees when token is not associated to fee collector
should fail when fee has negative values for non fungible token ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when fee has negative values for non fungible token
should fail when fee has negative values ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when fee has negative values
should fail when fractional fee has denominator zero ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when fractional fee has denominator zero
should fail when the provided fee collector is invalid for NFT ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided fee collector is invalid for NFT
should fail when the provided fee collector is invalid ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided fee collector is invalid
…

♻️ This comment has been updated with latest results.

[acuarica]

lg, but isn't this something that should be provided by local node? the forwarding to web3?

[quiet-node]

lg, but isn't this something that should be provided by local node? the forwarding to web3?

Yeah ha actually it's a good point. I think it's doable okay will create a ticket on local-node repo. Thanks for pointing it out!

[acuarica]

lg