Update Ops Showcase instructions

Why is this change being made?

Make adding new entries to the Ops Showcase simpler, by skipping the use of a gdoc entirely, and relying on epic-issue links as the SSoT of demos for each quarter.

This is a follow-up to the discussion in this MR: gitlab-org/ci-cd/section-showcases!6 (comment 1272209559)

I also updated the description of the epic to reflect the new instructions: FY24-Q1 Ops Engineering Showcase (&2099 - closed)

Before vs after

Screenshot - before

Screenshot - after

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.

---