Implement Meeting Permissions

[mattkrick]

Today, our meeting permission model is slightly broken. Some queries require a user be a part of the meeting. Others require that the user be a part of the team. This leads to a handful of bugs & some customer complaints.

I propose that each meeting has a visibility settings, similar to templates.
Possible options are:

• ONLY these people - select from a list (post-meeting, we could use this for things like closing it to only folks who attended)
• Anyone who joins the team before the meeting ends
• Anyone on the team
• Anyone in the org
• Anyone with a parabol account

We'll leave the UI out of it to keep the scope small.

AC

• Each new meeting has a scope field that is one of PUBLIC, ORGANIZATION, TEAM, TEAM_BEFORE_END, INVITEES. the mutation to start the meeting includes a scope arg
• a migration runs to add {scope: TEAM} to all existing meetings
• Each new Team created has defaultScope: TEAM on it
• a migration runs to add {defaultScope: TEAM} to all Team objects (putting it on Team vs. MeetingSettings because this seems more like a team culture thing than a meeting-type specific thing)
• a mutation exists to change the defaultScope. options include PUBLIC, ORGANIZATION, TEAM, TEAM_BEFORE_END
• when a meeting ends, timeline events & meeting summaries are sent to the invitees or team, depending on the scope
• When querying a meeting, an error is returned if the scope is incorrect for that viewer
• for TEAM_BEFORE_END, it requires that the teamMember.createdAt < meeting.endedAt

Estimate: 24 hours

[github-actions]

Stale issue

[mattkrick]

closing in favor of #4540