Add Community Forks note

Why is this change being made?

This MR adds a note stating that the GitLab Community Forks are not part of the bug bounty program. The GitLab Community group has been receiving requests from HackerOne users who are requesting access to the GitLab Community Forks to attempt to exploit vulnerabilities and seek rewards via the HackerOne bug bounty program. This may pose a security risk as users with Community Forks access could act maliciously.

Additionally the policy on the HackerOne account should be updated to make mention that the GitLab Community Forks are out of scope and not eligible for the bug bounty.

See recent access requests here:

• gitlab-community/meta#65 (closed)
• gitlab-community/meta#31 (closed)

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.

---