Alessio C. leave the ci_template maintainer role

Why is this change being made?

I think it's time for me to move on from this role. I became a CI template maintainer when I was a backend engineer in the very old CI/CD team. A lot has happened since then.

• We moved from vendoring templates to a single repository,
• @shinya.maeda did a fantastic job in introducing a structure to our CI/CD template review process
• @cheryl.li did an amazing job in building the CI templates maintainer and trainee group

With that said, my involvement in the review process has been always more marginal in the last period of time, and it's time for me to leave the maintainer role.

Thank you so much @shinya.maeda, @cheryl.li, @marcel.amirault, @matteeyah, and @lauraX keep up the good work! 🚀

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.

---