Description

This PR introduces the optional configuration parameter HeimdallWSAddress, which enables the application to establish a WebSocket connection with Heimdall for event listening rather than relying on polling. This enhancement aims to provide more efficient and real-time event handling.

Changes:

• New Config:
  Added HeimdallWSAddress as an optional configuration setting to allow connecting via WebSocket to Heimdall.

• WebSocket Integration:
  Updated the subscription logic to support event listening over a WebSocket connection. This change has been tested on a deployed devnet node, including a scenario where the connection is recovered after stopping bor.

• Code Refactor:
  In handler_bor.go, refactored the handle and fetch methods to better segregate their roles, improving code clarity and maintainability.

Changes

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)
• Changes only for a subset of nodes

Checklist

• I have added at least 2 reviewer or the whole pos-v1 team
• I have added sufficient documentation in code
• I will be resolving comments - if any - by pushing each fix in a separate commit and linking the commit hash in the comment reply
• Created a task in Jira and informed the team for implementation in Erigon client (if applicable)
• Includes RPC methods changes, and the Notion documentation has been updated

Cross repository changes

• This PR requires changes to heimdall
  • In case link the PR here: Milestone Events heimdall-v2#184
• This PR requires changes to matic-cli
  • In case link the PR here: Including ws address matic-cli#323

Testing

• I have added unit tests
• I have added tests to CI
• I have tested this code manually on local environment
• I have tested this code manually on remote devnet using express-cli
• I have tested this code manually on mumbai/amoy
• I have created new e2e tests into express-cli