Draft: Mention security issues in release blog only if they are released along with GitLab security release.

Why is this change being made?

There is no clear definition of security issues that qualify to be mentioned in the security blog. This MR brings clarity by suggesting that security issues fixed in GitLab products that are released along with the GitLab security release only get mentioned in the security release blog post.

This suggestion came out of a discussion from https://gitlab.com/gitlab-com/gl-security/appsec/appsec-team/-/issues/341+

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.
• 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
• 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.

---