Consider moving Group Conversations from doc to GitLab

From @bwill on Slack:

Would it make sense to host these on GitLab issues rather than Google docs since there's no longer a synchronous component? I find that issues are better for async collaboration but Google docs makes sense when you have both sync and async (because of live editing).

Creating this issue so we don't forget. If anyone wants to collaborate or take this on, please feel free, You can mention the Chief of Staff Team or post in the #ceo-chief-of-staff-team Slack channel.

Implementation plan

1. Have EBAs review the changes/MR as they are the ones who do the work on these. | Posted on Slack for review.
2. Create a private project, thinking gitlab-com/group-conversations, for issues to go into. Readme of the project should include links to handbook page, archive doc.
3. Create a default issue template which mimics the doc, including guidance on how to format the title so it's consistent.
4. Ensure drive folder is linked from the project readme as where to start when looking for an "archive".
5. Merge MR.
6. Draft Slack communications, and post in #whats-happening-in-gitlab, cross-post to #group-conversations.