Represent Security department structure in group list

Why is this change being made?

The list of sub-groups for GitLab sub-departments and teams did not reflect the current structure and was getting long and hard to read.

This MR also includes:

1. Proposed changes for an Engineering and Research Meta project similar to the convention used by teams like support gitlab-com/support/support-team-meta>.
2. Proposed structure for the sub-department and the Automation team tracker moved underneath, as follow up to this morning's call.

cc @laurence.bierner @gitlab-com/gl-security/automation

Changes to be made as a result of this MR

• Move gitlab-com/gl-security/automation to gitlab-com/gl-security/engineering-and-research/automation-team.
• Rename gitlab-com/gl-security/automation-team/tracker to gitlab-com/gl-security/engineering-and-research/automation-team/automation.
• Depending thread outcome: Move and rename gitlab-com/gl-security/automation/sec-auto-strategy to gitlab-com/gl-security/engineering-and-research/engineering-and-research-meta

Author Checklist

• Correct MR template applied (e.g blog post)
• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack