chore: Remove Outdated Sec Principal Priorities Page

Why is this change being made?

As discussed previously, this page is outdated and not an accurate reflection of the Sec Principal engineers priorities. While it was very useful in defining the initial goals when the role begin, it is not regularly updated and instead has performed some double-duty with section-wide priorities, which should ultimately be tracked in a different manner.

Per 1:1 discussion with @twoodham, 1:1 discussion with @pcalder, and previous sync with @sarahwaldner and @sam.white I'm proposing removal.

As a minimal change for accurately tracking my immediate priorities, I've been including areas of focus via my personal README with a current review cadence of every two weeks.

One of the related aspects of previous discussions on this topic was around maintaining a shared section-wide list of priorities. While this sounds useful and possibly orthogonal to our devsecops adoption priorities I feel that's out of scope of the nature of this change as the priorities of an individual role cannot be equated to the section's. See this discussion for more context there.

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

• chore: Remove Outdated Sec Principal Priorities Page

This list is outdated and while useful to align on initial priorities, doesn't accurately reflect areas of focus.

---