feat(abciclient): route abci requests depending on request type

[lklimek]

Issue being fixed or feature implemented

We want to have separate ABCI app instance for read-only operations, like check tx or query, and separate for
consensus operations like prepare/process proposal, finalize block, etc.

What was done?

Implemented RoutedClient that routes requests to one of multiple abci apps.
It can be configured by settings:

abci = "routed"
proxy-app = "Info:socket:unix:///tmp/socket.1,Info:socket:unix:///tmp/socket.2,CheckTx:socket:unix:///tmp/socket.1,*:socket:unix:///tmp/socket.3"

Documented in config.toml.

How Has This Been Tested?

Integrated into Dash Platform's rs-drive-abci

Breaking Changes

None

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[shumkov]

👍

The base branch was changed.

[shumkov]

👍