feat: added getErcTokenInfo() to retrieve detailed token information in the ERC Registry project.

[quiet-node]

Description:

• The ContractScanner service class now includes a new method, contractCallRequest(), which submits a contract call request to the mirror node targeting an ERC contract to fetch detailed standard token information such as name, symbol, decimals, and totalSupply.
• The ByteCodeAnalyzer service leverages the newly added ContractScanner.contractCallRequest() method to retrieve token information whenever a new ERC contract is detected.

Below is an example of the output ERC object written to the registry:

erc20:{
  "contractId": "0.0.15707",
  "address": "0x0000000000000000000000000000000000003d5b",
  "name": "CUSD",
  "symbol": "CUSD",
  "totalSupply": 0,
  "decimals": 18
},

erc721: {
  "contractId": "0.0.1778110",
  "address": "0x00000000000000000000000000000000001b21be",
  "name": "Genesis SpheraHead",
  "symbol": "SPH"
}

Related issue(s):

Fixes #1059

Notes for reviewer:

Checklist

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

[github-actions]

Test Results

 16 files  ±0   83 suites  ±0   12m 10s ⏱️ +39s
294 tests +5  288 ✅ +7  6 💤 ±0  0 ❌  - 2 
303 runs  ±0  296 ✅ +2  7 💤 ±0  0 ❌  - 2 

Results for commit 94bee74. ± Comparison against base commit 78fb1ee.

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

"before each" hook for "should fail when the provided fee collector is invalid" ‑ TokenManagmentContract Test Suite Update fees "before each" hook for "should fail when the provided fee collector is invalid"

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 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
should fail when the provided token id is invalid for NFT ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided token id is invalid for NFT
should fail when the provided token id is invalid ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided token id is invalid

♻️ This comment has been updated with latest results.

[acuarica]

lgtm