While working on the auto-join communities feature, I discovered an issue with the Farcaster channel tag blob hash method. The current setup allows the download of a Farcaster channel tag blob for a community not part of the keyserver.here the `commCommunityID` in the blob payload did not have the keyserverID:
```
farcasterChannelTagBlobs [
{
"commCommunityID": "83887",
"farcasterChannelID": "comm"
},
{
"commCommunityID": "145350",
"farcasterChannelID": "memes"
},
{
"commCommunityID": "83887",
"farcasterChannelID": "farcaster"
},
{
"commCommunityID": "83885",
"farcasterChannelID": "founders"
}
]
```
The Farcaster channel tag blob hash was composed solely of the farcasterChannelID. This means that if a user in Keyserver A creates a Farcaster channel tag for the /comm Farcaster channel, a user in Keyserver B, who also follows the /comm Farcaster channel, would receive the community info. However, this community would not be part of Keyserver B.
Since communities are localized to their keyserverthe the thread ids in the `threadInfos` look like this: `256|83843`, we should include the keyserver ID as part of the blob hash to ensure proper download blob functionality in a multikeyserver environment.
Depends on D12062here the keyserver id is appended to the front of the thread id and the two ids are separated by a pipe character. This diff updates the value of `commCommunityID` to follow this convention