Add recommendations around sharing internal incubation progress

Why is this change being made?

I really struggled to be transparent publicly over the last month while making changes to an internal project. It felt like I didn't have anything to share externally that iterated past what I shared in my most recent GitLab Unfiltered video outside updates I was sharing in the Engineering Week In Review internal document.

Only after my code shipped into the public component did I feel confident my update would be SAFE and substantially different from my previous demo. This shares some points that I could've shared mid-month to be more transparent publicly (rather than for only team members).

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---