Sliding Sync: Lazy-loading room members on incremental sync (remember memberships)

[MadLittleMods]

Lazy-loading room members on incremental sync and remember which memberships we've sent down the connection before (up-to 100)

Fix #17804

Follow-up/alternative to #17806

Depends on #17785

Pull Request Checklist

• Pull request is based on the develop branch
  • Wait for Correctly handle changes to required state config in sliding sync #17785 to merge
• Pull request includes a changelog file. The entry should:
  • Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
  • Use markdown where necessary, mostly for code blocks.
  • End with either a period (.) or an exclamation mark (!).
  • Start with a capital letter.
  • Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
• Code style is correct
  (run the linters)

[MadLittleMods]

It's possible that we could remember the specific state_keys that we have sent down before but this currently just acts the same as if a whole type was removed (same as simple_remove_type)

This is just a performance optimization though and the result would look like following:

Suggested change

	{},
	{
	EventTypes.Member: {
	"@user3:test",
	}
	},

Perhaps it's good that we "garbage collect" and forget what we've sent before for a given type when the client stops caring about a certain type 🤷.

[erikjohnston]

I think this makes sense! I am slightly worried about the increase in the size of the tables if we keep adding more and more members in there, but I'll have a little think about how we might make that more efficient.

[erikjohnston]

Thanks!

[MadLittleMods]

Woot! Thanks for the review @erikjohnston 🦎