ci: fall back to plain build frontend for odd-arch wheels

[bdraco]

What do these changes do?

Override CIBW_BUILD_FRONTEND=build for the build-wheels-for-odd-archs
matrix in .github/workflows/ci-cd.yml, so cibuildwheel uses plain pip
to drive the per-ABI builds for the QEMU-emulated odd arches
(aarch64, armv7l, ppc64le, riscv64, s390x x
manylinux/musllinux).

The project's pyproject.toml sets build-frontend = "build[uv]",
which requires a uv binary on PATH inside the build container.
The pypa tested-arch manylinux/musllinux images ship uv preinstalled,
but the odd-arch images (as of the 2026.03.20-1 tag) do not. Without
this override, every odd-arch musllinux job fails at
cibuildwheel: Command ['which', 'uv'] failed with code 1, which
fail-fast cancels the matching manylinux jobs.

Comment in reusable-cibuildwheel.yml updated to call out the split.

Are there changes in behavior for the user?

No user-visible API change. Keeps odd-arch wheels building on future
tagged releases.

Is it a substantial burden for the maintainers to support this?

No; the override is two lines in ci-cd.yml plus a comment update,
and can be reverted once the pypa odd-arch images ship uv.

Related issue number

Port of aio-libs/yarl#1720 to this repo.

Checklist

• I think the code is well written
• Unit tests for the changes exist; N/A, CI workflow change
• Documentation reflects the changes; N/A
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
• Add a new news fragment into the CHANGES/ folder

Agent run details (optional, for reviewers)

• The build-wheels-for-odd-archs matrix is gated on pre-deploy,
  which only runs on tag pushes; this change cannot be smoke-tested
  on a PR. Verification path is the next tagged release.
• pre-commit run --all-files ran clean on the commit.
• New terms added to docs/spelling_wordlist.txt for the news
  fragment: aarch64, armv7l, musllinux, ppc64le,
  preinstalled, s390x.

Drafted with Claude Code (Opus 4.7); reviewed by @bdraco before flipping out of draft.