Move Team Tags to their own field

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

To reduce confusion on downstream use of fields included within team member YAML files. This MR aims to seperate out the departments field into an additional team_tags field.

Previously, there was a mix of data sources:

• Department from Workday (updated automatically)
• List of custom departments/team tags (updated manually)
  • Some of these map to an associated team_tag from the stages.yml file.

Which leads to some mixes of team tags/departments in particular pages on the handbook. This change separates the concerns for us to be able to pull/update on individually.

With our changes in this MR this:

• Moves team tags from the departments list to their own field: team_tags

To Do

• Implement validation checks for team_tags
• Update any and all shortcodes that rely on team_members.departments field to use these new fields. gitlab-com/content-sites/handbook!11959 (merged)? should cover us.

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

• Move custom departments to team_tags

• Add script for creating team_tags field

---