encode shard fields in status.app links

[felicio]

note: blocked by https://github.com/waku-org/js-waku/issues/1310 note: blocked by https://github.com/status-im/status-go/issues/3954

what

• upgrade to @waku/sdk
• encode shard fields in community and channel URLs
• use shard fields to fetch the info
• use latest shard field to fetch the info if previous fetch returned it (relates to https://github.com/status-im/status-go/issues/3954)

---

notes

meeting

• pubsub topic where community/channel info is fetched from changes with the sharding feature (is tied to it), hence the fields are necessary
• desktop app in which sharding will be available (for testing) will be released sometime next week
• we'll use URLData layer of the protobuf instead of the entity one, which is for content (user facing informational value)
• edit: web changes issue: https://github.com/status-im/status-web/issues/464
• desktop/mobile changes issue: TBD c/o @Jo
• flag for tracking change in sharding state (newly sharded, not sharded, diff shard): https://github.com/status-im/status-go/issues/3954
• edit: no sharding for user info (now)
• edit: update spec in https://github.com/vacp2p/rfc/pull/600#discussion_r1305672545
• edit: new error states https://github.com/status-im/status-go/issues/3954#issuecomment-1693387247
• edit: shard implementation https://github.com/status-im/status-go/pull/3944