chore: Enabling to use a full node for lightpush via rest api without lightpush client configured

[NagyZoltanPeter]

Description

This is helper enhancment for testing (rate limit specifically for me) on lightpush... similar to query self store node via REST API. With this change one can issue lightpush request via REST API on a service node having lightpush protocol installed.

In contrast it was needed to run a full node with lightpush service and a light client (configured with the service node peerId) to be usable from REST API. With this change a lightpush service node (with relay of course) can serve such lightpush API request and can relay such messages.

This can help in various way.

• easy develop on REST API with nwaku-compose (where a full node is set up)
• easy test lightpush features via rest api.

Changes

• [X] /lightpush endpoint is enabled either lightpushclient or lightpush(protocol) mounted
• [X] lightpush protocol can handle such request by self hosted coming from REST API

How to test

1. Run a full node or nwaku-compose with the right image
2. issue REST /lightpush POST message
3. check that relayed (can depend on various stuff)

Open question:

• Currently relaying message via REST API will attach rln proof to the message. This is missing from lightpush, thus rest api user should be able to provide the proof.
• I think this can be think as, I'm using a thin layer towards the network via REST API by running a light node with my rln credentials. Such case lightpush service can attach proof to the message as in relay (REST API case).

[github-actions[bot]]

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2626-rln-v1

Built from 9787e539f1a3f4e407b73f64589631d3ccc2895a

[github-actions[bot]]

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2626-rln-v2

Built from 9787e539f1a3f4e407b73f64589631d3ccc2895a