Create page for devsecops tracking guidance

Why is this change being made?

direct guidance for CSMs on tracking devsecops adoption required

Author Checklist

• 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.
• 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
• 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.

---

sites/handbook/source/handbook/customer-success/csm/devsecops-adoption-tracking/index.html.md

@@ -22,3 +22,5 @@ description: "CSM guidance on how to track and log progress on DevSecOps usecase
    * Customer DRI listed in task
 1. Begin taking the customer through the steps within the DevSecOps playbook, offering both an enablement session on the [Get Started Guide](https://docs.gitlab.com/ee/user/application_security/get-started-security.html) and on our [DevSecOps & Compliance Features and Best Practices](/handbook/customer-success/workshops/secure/).  
 1. If a customer is not able to move forward with the implementation, change the status of the enablement CTA to 'blocked' and record the reason for being blocked in the comments section
+   * Record the date and reason for being blocked in the comments section
+   * Continue to update the comments section as new information pertaining to the blocked state is learned