odd order in initial system messages when secure-join is in progress

[adbenitez]

these chats are always encrypted and can't never fallback to unencrypted, I guess the odd order in which "this chat is e2e encrypted" message appear is a legacy precaution because other unencrypted messages could appear before the encryption gets established, but now it looks pretty odd, the "this chat is e2e encrypted" message should be the very first message in the chat, not like this:

in case you don't notice the problem: in both cases, the secure-join process was still pending, yet the "this chat is e2e encrypted" message following the "please wait..." message feels like the process already finished but that is not the case, and the in-progress message should be at the bottom of the chat so it is clearer this is what is going on right now and that is the reason you can't write to the group/contact yet

[iequidoo]

Just in case: a related issue (#7308 ) closed because the fix for it added complexity to the code. Probably we can fix this particular scenario in a simpler way. There's no need to guarantee that "Messages are end-to-end encrypted" is always the first message