Add categories for new Security Platform Management group

What change is being made?

This MR adds the following 3 categories for groupsecurity platform management

1. Security Testing Configuration
2. Security Asset Inventories
3. Security Testing Integrations

Why is this change being made?

With the recent sec section realignment, groupsecurity platform management is new and categories need to be established. The team's charter is:

Enable appsec and development teams to orchestrate and control their application security tools from within the GitLab platform, integrate seamlessly with external tools, and provide a frictionless, holistic operational experience across GitLab's suite of security offerings.

Approvals

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

• Chief Product Officer @david (post MR link in chief-product-officer once all others have approved)
• PLT Leader relevant to the affected Section(s) @hbenson
• The Product Director relevant to the affected Section(s) @dagron1
• The Engineering Manager relevant to the affected Section(s) @or-gal
• The Group Engineering Manager relevant to the affected Section(s) @rvider
• Director of Product Design @vkarnes

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Adding SPM categories

---