Implement MSC4023: Thread ID for 2nd order-relation in Synapse

[Johennes]

The proposal matrix-org/matrix-spec-proposals#4023 requires an implementation in Synapse.

This issue is part of the ongoing effort to fix stuck notifications in Element Web. As mentioned in @neilisfragile's engineering newsletter this week, we had to skip the last Element Web release because one of our client-side fixes has unhidden a larger battery of other issues that we have since been working on.

The biggest remaining issue we've narrowed things down onto this week is element-hq/element-web#25450. We've put in a client-side fix for this but the excess requests to fetch the unknown events have a performance impact. The size of the latter is hard to gauge but in our tests it was as bad as 5x in extreme cases.

After testing on today's nightly, we believe the general experience is good enough to unblock our release but preferably we'd like to limit the time window where performance is negatively impacted by leveraging server-side support through MSC4023.

[clokep]

A proof of concept can call RelationsWorkerStore.get_thread_id(...) for each event returned.

I think we would ideally want to calculate this for every event and store it. (I guess in the events table?) This is a bit tricky though since you might know about events A; C (which relates to B as a reaction). Then later find out that event B is a thread. So you need to retroactively add C from the main timeline to the B timeline.