Update job example for quick methods related to JTBD

Why is this change being made?

The example provided as a quick method for increasing confidence about a JTBD conflicts with guidelines elsewhere in the handbook.

.. ask questions based on the JTBD such as, "tell me about the last time you created a multi-stage pipeline. What went well? What didn't go so well?"

Is that a job or job statement? Pipelines are a solution. We discourage including solutions in the JTBD.

What does the job performer want to accomplish (independent of your solution)?
The aim of the job performer is not to interact with your company but to get something done. Because they don’t mention solutions or technology, jobs should be as timeless and unchanging as possible. Strive to frame jobs in a way that makes them stable, even as technology changes.
- source

Comment thread: #12747 (comment 750694400)

Author Checklist

• Provided a concise title for the 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 change to the correct DRI(s)
  • 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 in 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.

---