feat: use 1 content-topic for all chats within a community (not to merge)

[chaitanyaprem]

Summary

This PR is mainly to dogfood underlying changes made in status-go.

Reference PR status-im/status-go#5864 which has details.

This PR uses single content-topic for all community chats to send messages. It still receives messages on all existing content-topics used by previous versions in order to maintain compatibility.

Details of the discussion are available https://forum.vac.dev/t/status-communities-review-and-proposed-usage-of-waku-content-topics/335/29

Testing notes

Platforms

• Android
• iOS

Areas that maybe impacted

Community chats and control flows

Functional

• public chats
• all community chats and control flows (channel creation, updation, deletion, permissions change, user add, user kick etc)
• new account

Steps to test

• This PR would require complete testing of communities in relay and light modes.
• It would also require to be tested for compacibility with older version of the code.
• Best to check all admin functions as well using this new code
• We also need to validate if community admin is using older code and a member is using new code there are no incompatibilites.
• All chats and community flows such as add member, remove member, add channel, delete channel, change permissions to channels etc

Risk

Described potential risks and worst case scenarios.

Tick one:

• Low risk: 2 devs MUST perform testing as specified above and attach their results as comments to this PR before merging.
• High risk: QA team MUST perform additional testing in the specified affected areas before merging.

-->

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	a0930bf	#1	2024-10-09 10:38:32	~5 min	tests	📄log
✔️	a0930bf	#1	2024-10-09 10:41:35	~8 min	android-e2e	🤖apk 📲
✔️	a0930bf	#1	2024-10-09 10:42:45	~9 min	android	🤖apk 📲
✔️	a0930bf	#1	2024-10-09 10:43:21	~10 min	ios	📱ipa 📲

[churik]

Blocking it until 2.31 is cut