matrix: Add room retention policy

[backspace]

This adds a retention policy to auth rooms created by a realm Matrix user. It also backfills the policy to existing rooms, this can be deleted after it has run in production. I already ran it in staging, you can confirm that your user’s rooms have a policy with this script after having stored matrix-service in $E via Ember Inspector:

roomRows = [];
for (r of (await $E._client.getJoinedRooms()).joined_rooms) {
    roomRow = {roomId: r};
    roomRows.push(roomRow);

    roomRow.members = (Object.keys((await $E._client.getJoinedRoomMembers(r)).joined).join(', '));
    try {
      await $E._client.http.authedRequest('GET', `/rooms/${r}/state/m.room.retention`);
      roomRow.hasRetention = (true);
    } catch(e) {
      roomRow.hasRetention = (false);
    }
}

console.table(roomRows);

(This would only apply for users that existed when this branch was deployed.)

[github-actions]

Host Test Results

    1 files  ±0      1 suites  ±0   21m 41s ⏱️ +36s
729 tests ±0  727 ✔️ ±0  2 💤 ±0  0 ❌ ±0 
734 runs  ±0  732 ✔️ ±0  2 💤 ±0  0 ❌ ±0 

Results for commit 26c0aaa. ± Comparison against base commit fc4cc23.

♻️ This comment has been updated with latest results.

[backspace]

I don’t love having this duplicated vs importing the constant from runtime-common but if you look at the CI history you can see a type-checking can of worms 😞

[lukemelia]

I ran into the same challenge with matrix event name constants

[backspace]

ugh… it’s really a shame, I just lack the understanding of how to get through the typechecking minefield

[lukemelia]

Maybe create an issue to review this with @ef4

[lukemelia]

I ran into the same challenge with matrix event name constants