feat: design automated smart contract ABI registry and parser (#441)

[Danielodingz]

Closes #441

Description

This PR introduces the standalone implementation of the Automated Smart Contract ABI Registry and Parser. As per the maintainer's instructions, this has been encapsulated in a dummy directory (backend-abi-registry) that contains all the required MVP-critical architecture, ready to be inserted into the correct backend location (e.g. indexer or keeper) when needed.

Feature Overview

• Monitor: A resilient polling system to continuously check for newly deployed contracts.
• Parser: A stateless extraction module that safely parses and standardizes ABIs from raw bytecode.
• Registry: An in-memory, searchable registry that supports reverse-lookups by function name.

Implementation Requirements

• Fault-Tolerant Pipeline: Robust error boundaries are implemented across all components.
• Thorough Error Tracking: A centralized errorHandler intercepts and logs all failures to enable fallback mechanisms securely.
• High Test Coverage: Achieved 97.46% test coverage (passing the >90% requirement) using Jest.
• Strict Architectural Boundaries: Completely decoupled components mimicking production microservice constraints.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The test suite ensures >90% coverage for the entire ABI parser pipeline.

• Unit tests for Parser and Registry (Mocked data, simulated parsing errors)
• Unit tests for ErrorHandler
• Integration tests for Monitor connecting the pipeline and validating graceful degradation during simulated network failures.

Test Configuration:

• Run npm test inside the backend-abi-registry folder to see coverage reports.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[drips-wave]

@Danielodingz Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Danielodingz]

Hello @ayomideadeniran please review and merge. Thank you