encode shard fields in status.app links

[felicio]

note: blocked by waku-org/js-waku#1310
note: blocked by status-im/status-go#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 sharding: community migration to different shard and links status-go#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: encode shard fields in status.app links #464
• desktop/mobile changes issue: TBD c/o @jo
• flag for tracking change in sharding state (newly sharded, not sharded, diff shard): sharding: community migration to different shard and links status-go#3954
• edit: no sharding for user info (now)
• edit: update spec in feat(59/STATUS-URL-DATA): initial draft vacp2p/rfc#600 (comment)
• edit: new error states sharding: community migration to different shard and links status-go#3954 (comment)
• edit: shard implementation waku2: static shards status-go#3944