Do not show membership/profile/topic events in public rooms

[bxdxnn]

See element-hq/element-x-android#6360

Checklist

• I have read through review guidelines and CONTRIBUTING.md.
• Tests written for new code (and old code if feasible).
• New or updated public/exported symbols have accurate TSDoc documentation.
• Linter and other CI checks pass.
• I have licensed the changes to Element by completing the Contributor License Agreement (CLA)

[t3chguy]

Please write tests before seeking review

[t3chguy]

@bxdxnn bxdxnn force-pushed the feature/no-member-events-flood branch from 92c71ca to 590238c
2 days ago

Please read the contributing guide again.

https://github.com/element-hq/element-web/blob/develop/CONTRIBUTING.md#:~:text=Please%20do%20not%20use%20force%20push%20in%20your%20PRs.%20Doing%20so%20means%20we%20can%27t%20see%20what%20has%20changed.%20We%20use%20squash%20merge%20to%20get%20a%20%22clean%22%20git%20history.

[t3chguy]

Dismissing code review until Product reviews it

[bxdxnn]

@bxdxnn bxdxnn force-pushed the feature/no-member-events-flood branch from 92c71ca to 590238c
2 days ago

Please read the contributing guide again.

https://github.com/element-hq/element-web/blob/develop/CONTRIBUTING.md#:~:text=Please%20do%20not%20use%20force%20push%20in%20your%20PRs.%20Doing%20so%20means%20we%20can%27t%20see%20what%20has%20changed.%20We%20use%20squash%20merge%20to%20get%20a%20%22clean%22%20git%20history.

Sorry, I was thinking you didn't review it.

[mxandreas]

As I already commented on the Android PR, this topic need comprehensive handling not local patches for specific use cases or pain: element-hq/element-x-android#6360 (comment)

From product/design perspective we can't accept this as is.