Add deprecation and removal section to Gitaly Direction

Why is this change being made?

This change adds the deprecation and removal tracking epic for Gitaly to the Gitaly Direction Page.

Closes #13051 (closed)

Author Checklist

• 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
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this change to the correct DRI(s)
  • 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 in 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.

---

source/direction/create/gitaly/index.html.md

@@ -278,6 +278,14 @@ Customers may not desire to utilize Gitaly Cluster for the following reasons:
 As we [mentioned above](https://about.gitlab.com/direction/create/gitaly/#improved-documentation-for-gitaly-and-gitaly-cluster), one of our priorities is to improve the Gitaly Cluster documentation. In order to do this, we would appreciate any problems be raised as an issue under our [documentation epic](https://gitlab.com/groups/gitlab-org/-/epics/5075). Additionally, if you receive assistance from the Gitaly team in resolving a customer issue, please help us clarify our documentation to help future teammates and customers.
+## Deprecations and Changes
+
+As Gitaly and Gitaly Cluster evolve, it is sometimes necessary to deprecate features. When this occurs, we will follow the documented [Deprecations, removals and breaking changes](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes) procedure. This ensures that all stable counterparts within GitLab are informed, and that the [GitLab Documentation](https://docs.gitlab.com/ee/update/deprecations) is also updated to keep our customers informed.
+
+In addition, we will track all deprecations throughout the 14.x milestones, and breaking changes occurring in the 15.0 milestone on the following epic:
+
+- [Gitaly 14.x through 15.0 Deprecations and Removals](https://gitlab.com/groups/gitlab-org/-/epics/7552)
+
 ## Top Customer Success/Sales issue(s)
 <!--