Shift in priority for license component filter

Why is this change being made?

1. Update based on gitlab-org/gitlab#413535 (comment 1941270783)
   1. Pull in external status check response audit events
   2. Include authentication for external status checks - gitlab-org/gitlab#433035
   3. With our ownership now of status checks, these are causing large concerns for many customers surrounding compliance and they are low hanging fruit. This will also help us with future efforts in gitlab-org&10177 while adding some value for customers today.
2. Updating priority to have TBD on some plans that aren't ready for dev. Considering that we revisit the list of priorities to only supply a milestone date when we feel we can commit to it, or differentiate it with another field for start date without a target completion date.
3. Remove tech debt epic as we will work on smaller improvements like this in small increments each milestone.
4. Adds gitlab-org&14057 - this is a compliance gap affecting both SEP and PEP, hence it will need to be a higher priority.

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

• Shift in priority for license component filter

---