test: nwaku nodes started on The Waku Network requires a RPC endpoint

[danisharora099]

Problem

Within our tests suite, we have tests that also attempt connection with nodes started on cluster ID = 1 and after the v0.26.0 update, it expects a RPC endpoint passed along to fetch contract re data.

Proposed Solutions

• Use a public RPC endpoint that we can also push to GH without any security concerns
• Use environment variables for the RPC endpoint

[rymnc]

something that is tangentially related to this issue, please ensure that the rln_tree is persisted across runs so the nwaku nodes finish sync and startup quicker

[danisharora099]

something that is tangentially related to this issue, please ensure that the rln_tree is persisted across runs so the nwaku nodes finish sync and startup quicker

Good point!

[weboko]

Moving to Priority as we need to address it sooner than later.
For now tests are using different cluster IDs to avoid nwaku nodes from failing to run.

[weboko]

@fbarbu15 can you, please, give your input on this issue?

In particular, if we foresee many tests in future to use this?

[fbarbu15]

On the interop testing side we use cluster id 1 only to test RLN. So the testing around this cluster is contained. Tests on this cluster id are also more complex and slower (node can take more than 1 minute to fully start) because of RLN so it's another reason to avoid it.
So I think it will be the same case for js-waku tests

[weboko]

Summarizing - we foresee such tests in js-waku in future but not now.
@adklempner merged the PR and the job is now skipped in CI.

Once it is needed I think QA team will re-enable this step and will update with needed changes.

Closing as complete.