feat: allow subscribeToContentTopic to use other cluster IDs

[fbarbu15]

This is a change request

Problem

subscribeToContentTopic starts a new node with partial ContentTopicInfo (no clusterId) so createLightNode will resolve clusterId to DEFAULT_CLUSTER_ID=1
But Autosharding will be possible on other cluster IDs as well with waku-org/nwaku#2502

Proposed Solutions

Allow clusterId as a parameter in subscribeToContentTopic

[chair28980]

Blocked by waku-org/nwaku#2502

[fbarbu15]

This was fixed on nwaku side here

[weboko]

Moving to the top of Todo column to be taken next once release related and reliability bugs are done.