Move communities' control and content to separate shards

[plopezlpz]

As specified here:

https://github.com/vacp2p/rfc-index/blob/0277fd0c4dbd907dfb2f0c28b6cde94a335e1fae/status/56/communities.md?plain=1#L319C1-L328C89

1. All messages with a global community control scope MUST be published to shard 128
2. All messages with a global community content scope MUST be published to shard 256

• Write a migration strategy:

Stages:

• Listen to 128 and 256 together with the current shards: feat: communities-in-own-shard-1 #6573
• Publish communities' messages on those shards: feat(sharding): stage2 sending in new communities shard #6588
• (Cleanup): Stop listening for communities' messages in old shards

[plopezlpz]

List of all message types to shards by @kaichaosun https://docs.google.com/spreadsheets/d/1wvlgTw9QyoheElNvJu_aPT-iwlJY8_EYxXcC1rEZbwo/edit?usp=sharing