[RelayMiner] Add an ability to test RelayMiner configuration without application

[okdas]

Objective

The current Morse mainnet client has a feature to send relays without application signature. We should add this functionality to RelayMiner: an ability to send relay through a supplier without providing meta information (session, signature, etc.) so operators can verify their RelayMiner configuration.

Origin Document

Requests from the community:

• Discord;

First mentioned in internal communication.

In the current Morse client, the feature is enabled by adding --simulateRelay argument. In our implementation, we can consider adding this to the relayminer config file.

Goals

• Operators can configure their RelayMiners to send requests to the backend service to make sure applications will get expected service.

General deliverables

• Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
• Testing: Add new tests (unit and/or E2E) to the test suite.
• Makefile: Add new targets to the Makefile to make the new functionality easier to use.
• Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.

---

Creator: @okdas

[Olshansk]

@okdas to provide a link to pocket-core and an example of how it works on Morse.

[okdas]

In pocket-core guidelines, we recommend node runners to start the process with --simulateRelay prior to staking, so they can test before going live. That way, they would avoid being ignored by the gateway (or getting jailed/slashed - though I don't think this is functionality is turned on).

This argument then adds a new http route where the relay simulation request can be sent to. For example, this is how I used to do that:

Fuse

curl -X POST \
--data '{"relay_network_id":"0005","payload":{"data":"{\"jsonrpc\":\"2.0\",\"method\":\"eth_blockNumber\",\"params\":[],\"id\":0}","method":"POST","path":"","headers":{}}}' \
http://localhost:8081/v1/client/sim

xdai

curl -X POST \
--data '{"relay_network_id":"0027","payload":{"data":"{\"jsonrpc\":\"2.0\",\"method\":\"eth_blockNumber\",\"params\":[],\"id\":0}","method":"POST","path":"","headers":{}}}' \
http://localhost:8081/v1/client/sim

I think we have an opportunity to make this functionality more user-friendly and still secure at the same time. The simplest way to implement I think would be to add some sort of "password" or a token that can be passed via HTTP header.