After I typed MessageSQLResultRow, Flow started complaining for both of these.

Technically the old code was safe... JS has quirky behavior with objects where it basically casts all number keys to strings, and the collapse_key is guaranteed by the query to always be set (collapseQuery specifically queries for results that have a collapse_key set to a specific value)

(I could have created a different type for the result of collapseQuery, but didn't seem that important)

This is necessary because technically id is nullable – in fetchCollapsableNotifs, if a notif points to a message that is missing in the messages table, this can happen. In that case we will just skip that message when fetching the collapsable notifs.

(If this DB corruption occurred previously, we would have thrown an exception... so this probably counts as Flow identifying a type error)

This await (and all the ones below) are not necessary because parseMessageSQLResult does not return a Promise.

Flow didn't notice this since it's technically valid JS (await a non-Promise just returns it back), but there's no reason to suspend execution here, so I removed the await keywords