fix(federation): Sync room properties on join

[nickvergessen]

☑️ Resolves

• Fix Recording consent not offered by the frontend if local server doesn't have it #13045
• Fix Initial state of federated room may not match the current state of the remote room #13060
• Ref Federated users are not aware of changed permissions #12953 (fixes room permissions, but individual participant permissions still need manual syncing like attempted in Propagate permission changes to federated servers #12979 )

Follow-up ideas

• Track a "property-version" so that recipients know if the just now received data is newer or older Possible inconsistent state between federated room and remote room if a cloud notification is retried #13079
• Always send the full room object when the room was modified, so the sync can heal other properties as well Possible inconsistent state between federated room and remote room if a cloud notification is retried #13079

🛠️ API Checklist

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not possible
• 📘 API documentation in docs/ has been updated or is not required
• 🔖 Capability is added or not needed

[nickvergessen]

/backport to stable30

[danxuliu]

I am not fully convinced on adding a specific method to update the database in a single query. While saving database queries is of course good, not many queries might be saved with that, so the standard RoomService methods could be used instead. In the initial sync it may help, but after that it would only help if some cloud notification is missed, as right now it syncs more properties than what is explicitly propagated (for example, the call recording state), but those missing properties should be propagated anyway; otherwise a federated user already in the room would not receive the change until another federated user joins again.

Syncing all the properties in one go in general seems to have the same effect as using the standard RoomService methods, but not sending the individual modification events could also miss some behaviours (like invalidating the reference cache), and there could be also missing behaviours on some specific methods (like resetting the participant permissions when the room permissions are modified). So I am not sure if the few saved database queries are worth the trouble of handling those things 🤔

Independently of that, CI does not seem to be happy.

[nickvergessen]

I am not fully convinced on adding a specific method to update the database in a single query.

my main intention was to avoid certain reactions of other components listening to the hooks
e.g. I don't know what happens if clients receive 10 room-modified signaling messages in few milliseconds and some of them with potential wrong/old data on other props
but I will just add a "before" event and make that one disable the normal RoomModified listener for signaling. Other listeners can decide themselves whether they should "pause" and conclude with a summary.
Should work just as fine

[nickvergessen]

Most of red CI is due to nextcloud/server#46991

[nickvergessen]

Changed it to the RoomService methods now, made the SignalingListener pause on BeforeRoomSync and send a single signaling messages afterwards.
Some other listeners were modified to not trigger on federated conversations (we don't need to check/stop a recording, etc.)

[nickvergessen]

• Just for the record, permissions are not handled in this PR, I will do that in Propagate permission changes to federated servers #12979 after rebasing it on this one

[danxuliu]

Force pushed to fix the check against the last activity.

I have also added a fixup, but not applied it yet, to update the lobby. Before only the lobby state was checked, but not the timer. Therefore, if the lobby was previously set but only the timer changed when the data was synchronized again it was not updated. But given that there was a condition inside the external if that took into account the timer maybe I am missing something, so I prefered not to apply it without a review from @nickvergessen

Other than that and the comment, tested and works 👍