Remove old processes from Enablement handbook page

Why is this change being made?

I propose we remove a couple of sections from the Enablement handbook page:

• Dogfood roadmap in planning - We still want to encourage teams to do this, but I think it's probably best for individual teams to document how they use the epic roadmap in their own pages and be responsible for keeping those links updated.
• Long standing merge requests - This is still something important for EMs to follow up on. However, there is now a triage ops report for Idle MRs to remind EMs to check up on any MRs idle for 30+ days. So I think we can remove this section and defer to that process which is QE driven.

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

---