Fix the 404 read-team link in the lead onboarding template

[ale210]

Overview

We need to correct a link in the lead onboarding template that points at a GitHub team which does
not exist, so that whoever onboards the next lead is not sent to a 404 while trying to grant
access.

Action Items

• In .github/ISSUE_TEMPLATE/onboard-ops-cop-lead.md, change the "read team" link from
  https://github.com/orgs/hackforla/teams/devops/members to
  https://github.com/orgs/hackforla/teams/devops-read/members. There is no team with the
  slug devops; the read team is devops-read. Confirmed by API 2026-08-27.
• Leave the "write team" link alone — devops-write on the line above is correct.
• After the PR merges, click the link from the rendered template and confirm it loads the team
  page.

Resources/Instructions

• File: onboard-ops-cop-lead.md,
  under the GitHub heading of the Onboard Checklist. Find it by the link text "read team" rather
  than by line number.
• Verify with gh api orgs/hackforla/teams/devops-read (succeeds) versus
  gh api orgs/hackforla/teams/devops (404).
• Sequencing: Finish the ops to devops rename in the CoP lead onboarding templates and the CoP: Ops label #190 renames this same file to onboard-devops-cop-lead.md.
  Whichever merges second must use the other's filename. Check Finish the ops to devops rename in the CoP lead onboarding templates and the CoP: Ops label #190's state before starting.
• The default branch of devops is master, not main.

[Amiirhosseini]

Hi — I'd like to take this issue.

Plan: Update the read-team link in .github/ISSUE_TEMPLATE/onboard-ops-cop-lead.md\ from \devops\ to \devops-read, leave the write-team link unchanged, and verify with \gh api orgs/hackforla/teams/devops-read\ before opening a PR. I'll also check the status of #190 first so I use the correct filename if that rename has merged.

Please assign this to me if available.