Document Developer Evangelism updates Slack channel with Zapier Automation

Why is this change being made?

The GitLab blog is a great resource for Developer Evangelists and social queues. We started automating the posts into the Discourse forum. We could also use it in Slack to get notified about new content. Currently, this involves manually checking the blog.

The UTM Campaign manager in the community apps helps to track metrics.

The Twitter algorithm changes caused that we do not see our team's tweets to amplify again. This needs manual shares.

This MR documents the newly installed Zapier automation Zaps for Developer Evangelism:

• Parse the GitLab Blog RSS feed and post updates into the #developer-evangelism-updates Slack channel
• Read the Twitter feed from @abuango @dnsmichi @sugaroverflow @johncoghlan and filter for @gitlab only the shares that need amplification, into Slack. Twitter unfortunately uses its own URL shortener that overlaps with go.gitlab.com

Additionally, all Developer Evangelism specific Zaps are moved into a sub-folder of Community relations in Zapier.

This should help us getting more efficient content items, and help each other amplify better.

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.

---