INVITATIONS: 'Group issue' for live release of join pop-up related issues

[BeccaMelhuish]

These issues are all interconnected, relating to join pop-ups (both email and share link ones) and should be released to production at the same time.

I.e. none of these should be released to production, until all the rest have been approved in QA pre-live and also in user testing.

• INVITES: Swap order of 'join' pop-up and login - join first, then log in #1700
• INVITES: When users click X on 'join topic/join group', they get a blank screen #1701
• MISC: User confusion on arriving into Citizen OS platform via invite link / reluctance to register first #1376
• INVITATIONS: Header image not being resized (Sub-issue of #1376) #1905
• INVITATIONS: Text intro, admin info, description and header image missing from topic invitation (Sub-issue of #1376) #1908
• INVITATIONS: Test join pop-ups with 500 characters once #1926 is fixed #1927
• IDEA GATHERING: Different topic invitations when logged out and logged in (sub-issue of #1376) #1932
• INVITATIONS: Logged out clicks view without joining but doesn't see the button to join topic/group #1894
• INVITATIONS: Change invitation pop-up titles to 'Join group' and 'Join topic' (Sub-issue of #1376) #1904
• IDEA GATHERING: Email topic invitation different from group (Sub issue of 1376) #1930
• INVITATIONS: Testing email invite flows and join pop-ups (sub-issue of #1376) #1910

These ones are also related, but can be released separately (no need to hold the above issues for them):

• INVITATIONS/LOGIN: When swapping login and join pop-ups in flow, should be a login pop-up not a login page #1911
• INVITATIONS: User has to click Join Topic twice after clicking View without joining (Sub-issue of #1376) #1900
• INVITATIONS: 'New to Citizen OS?' missing from new join pop-ups (sub-issue of #1376) #1948

Product team next steps for these I think would be:

• @DiverVM as you were working on these, if you spot something I have missed please flag it :)
• @ssin1901 I'm putting this one into QA pre-live, but for now it can just wait there, until we are ready to use it to check all is in order for the code release.
• Once I've done the user testing and confirmed that this is all making sense and working for users, then @ssin1901 could go through and confirm (using the tickboxes) when each of them is approved in pre-live as ready for release?
• Once we have the approval from both me and @ssin1901, and the branch merging issues are definitely resolved, then @ilmartyrk would release them to the code.
• If we have any more relevant issues come up in the meantime, I will add them to the above list.