chore: waku sync full topic support

[SionoiS]

update to the Waku sync spec to include full topic support.

[jm-clius]

LGTM. Comment to address before merging below - we have to be explicit about "topic" as being pubsub topic, content topic or both. Suggestion is to limit spec only to behaviour for pubsub topic, which will allow it to undergo full testing and QA separately to reach draft status while we experiment with content topics in parallel (which IIUC may necessitate more comprehensive storage changes).

[Ivansete-status]

Thanks for it!
I think we should avoid using the term pubsub outside the nwaku codebase.
From API pov, I'd only use these terms:

• timestamp
• cluster-id
• shard
• content-topic

[SionoiS]

Thanks for it! I think we should avoid using the term pubsub outside the nwaku codebase. From API pov, I'd only use these terms:

• timestamp
• cluster-id
• shard
• content-topic

I don't have strong opinions here we can either;

• use pubsub and content topics
• use cluster, shard and content topics

I think @jm-clius want the spec to be agnostic to network definitions?

[jm-clius]

I don't have strong opinions here we can either;

• use pubsub and content topics
• use cluster, shard and content topics

I think @jm-clius want the spec to be agnostic to network definitions?

Most of our core level specs use pubsub_topic as the mapping to pubsub topic from cluster ID and shard is a higher-level function. That said, I'm OK with use moving to cluster ID + shard throughout this spec, as long as we're consistent and do not refer to any specific deployment (e.g. TWN)

[SionoiS]

Most of our core level specs use pubsub_topic as the mapping to pubsub topic from cluster ID and shard is a higher-level function. That said, I'm OK with use moving to cluster ID + shard throughout this spec, as long as we're consistent and do not refer to any specific deployment (e.g. TWN)

I'm lazy and I don't want to change it back to shard again so I'll leave it like this.

[SionoiS]

I removed cluster and left only pubsub and content topics