Support: Document ZD's built-in limit ignoring our skip-tags

Why is this change being made?

Documenting the content of a Slack discussion to avoid future confusion about how the skip_ tags actually work.

• check https://handbook.gitlab.com/handbook/support/readiness/operations/docs/zendesk/tickets/#ticket-statuses for better fit of this change
• and https://handbook.gitlab.com/handbook/support/workflows/working-on-tickets/

We could alternatively also delete/undocument them here and open an STM issue to discuss other relevant changes if we decided to remove them from ZD itself (after having kept them during Zendesk Cleanup and Revamp: Tag changes (gitlab-com/support/support-team-meta#2959 - closed)).

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
  • Division: If the update affects your division, share the MR in your division 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

---