Update the JTBD for Pipeline Authoring

Why is this change being made?

I think we should edit this JTBD I want to create CI job templates so the teams in my organization could use it while creating their CI/CD pipelines. to be more solution agnostic and to focus more on the specific pain point/ job that needs to be solved. Once we mention a template it's already solution specific. Who knows, maybe one day we won't have templates but something else to solve that pain. Being more solution agnostic can help us innovate. ✨

Based on the insights that keep coming out of the customer interviews I propose to use When implementing CI/CD practices across the organization, I want to ensure consistency and standardization of CI/CD workflows to ensure compliance and to ease and increase CI/CD adoption across my teams.

Any suggestions to improve it are welcome! ☺

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
• Assign this change to the correct 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 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)