feat: Explorer could interpret Solidity method selectors

[ericleponner]

Description:

With changes below, Explorer now queries 4byte.directory and tries to decode call input/output. Contract Result and Call Trace sections in Transaction Details are now able to display decoded input and output even if corresponding contract is unverified.

Changes also include additional unit tests for FunctionCallAnalyzer class.

Note: Event decoding is not handled by these changes ; this will be done in a second phase.

Related issue(s):

Fixes #696

Notes for reviewer:

This transaction gives a pretty good view of the feature (see Call Trace section).

Checklist

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

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	85.39%	34395 / 40276
🔵	Statements	85.39%	34395 / 40276
🔵	Functions	65.4%	815 / 1246
🔵	Branches	84.15%	3852 / 4577

File Coverage

File	Stmts	% Branch	% Funcs	% Lines	Uncovered Lines
Changed Files
src/components/values/FunctionInput.vue	68.5%	50%	100%	68.5%	28-65, 71-72
src/components/values/FunctionResult.vue	83.8%	50%	100%	83.8%	28-42, 48-49
src/utils/analyzer/FunctionCallAnalyzer.ts	95.48%	83.33%	100%	95.48%	159, 190, 221-222, 238-240, 244, 251-252, 258-260, 313-315
src/utils/cache/CacheUtils.ts	100%	100%	100%	100%
src/utils/cache/SignatureCache.ts	97.56%	80%	100%	97.56%	44-45

Generated in workflow #692

[sonarqubecloud]

Quality Gate failed

Failed conditions

0.0% Coverage on New Code (required ≥ 80%)
23.7% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[svienot]

Looks good to me!