Improve tool sets for UI development

[shuse2]

Description

• Update APIClient to be able to connect to any application created using Lisk-SDK without plugins.
• Add utility functions to be used in UI development
• Add integration tests to check the functionalities in browser and mobile environment

Motivation

• Lisk-service can connect to the lisk-core outside of the process/machine
• Developer should have access to all the actions/events from framework, modules, and plugins through APIClient
• Mitigate the problem of most of the plugins require having different HTTP API server
  Imagine “reportDelegateMisbehavior” or “monitor” plugins don’t require REST API endpoint, but define action and it can be called through APIClient
• The native actions and events from framework related to block/transaction/account are encoded, so it would be useful if APIClient takes care automatically
• Lisk-core should use the APIClient, too, as it has custom implementation now.

Acceptance Criteria

• APIClient should not depend on any plugins or modules
• APIClient should not support any specific plugins or modules
• Accessing from browser and node.js environment must be supported
• It should be usable from lisk-core
• All the actions/events from framework, modules, and plugins should be accessible
• Allowing external communication in framework must be optional and disabled by default

Tasks

Sprint 31

• Create base32 and binary address conversion functions Create base32 and binary address conversion functions #5842
• Add getUnlockings action on dpos module Add getUnlockings action on dpos module #5843
• Add utility function getMinFee to lisk-transactions library Add utility function getMinFee to lisk-transactions library #5673
• Add WS server on framework and update application config Add WS server on framework and update application config #5920
• Update actions/events communication format to JSON-RPC Update actions/events communication format to JSON-RPC #5918
• Add basic scaffold and types for APIClient Add basic scaffold and types for APIClient #5922
• Implement IPCClient connection and base functions for APIClient Implement IPCClient connection and base functions for APIClient #5923
• Implement node namespace for APIClient Implement node namespace for APIClient #5925
• Implement block namespace for APIClient Implement block namespace for APIClient #5926
• Implement account namespace for APIClient Implement account namespace for APIClient #5927

Sprint 32

• Test Lisk client compatibility with client-side environments Test Lisk client compatibility with client-side environments #5714
• Integrate WS server with controller and enable channel communication Integrate WS server with controller and enable channel communication #5921
• Implement transaction namespace for APIClient Implement transaction namespace for APIClient #5924
• Implement WSClient connection for APIClient Implement WSClient connection for APIClient #5928
• Update Pom plugin to expose endpoint in action and remove http server Update Pom plugin to expose endpoint in action and remove http server #5945
• Update monitor plugin to expose all non-prometheus endpoints to actions Update monitor plugin to expose all non-prometheus endpoints to actions #5944
• Fix prometheus api data Fix prometheus api data  #5941
• Add basic scaffold and types for APIClient Add basic scaffold and types for APIClient #5922
• IPCClient should be able to connect to running node IPCClient should be able to connect to running node #5975