RLN key mechanism and proofs for all publishers

[chair28980]

Ensuring that on all Waku clients publishers can:

• manage RLN membership(s) and keys
• generate and attach RLN proofs when using any publishing API calls (lightpush, relay, etc.)

Owner: @rymnc (but delegate implementation ownership for different Waku clients)

Priority: Critical for launch

[rymnc]

Addressed as a part of waku-org/nwaku#1906 - under which -

• the rln_keystore_generator was added to create and register credentials to the rln membership set:
  • feat: rln subcommands go-waku#654
  • feat(rln): init rln_keystore_generator nwaku#1925
  • chore(rln_keystore_generator): generate and persist credentials nwaku#1928
  • feat(rln_keystore_generator): wired to onchain group manager nwaku#1931
• and proofs are attached thru api calls (rest + json-rpc):
  • chore(api): validate rln message before sending (rest + rpc) nwaku#1968
  • test(rln-relay): rpc handler to support waku rln relay nwaku#1852

[rymnc]

I cannot close this issue, so please do :)

[chair28980]

Closing per @rymnc's comment.