Fix Cua Driver release discovery across feed pages

[f-trycua]

Scope

Follow-up to #306, targeting its add-cua-driver-bin branch so Spencer's original package and authorship remain intact. This PR contains only the release-discovery fix and its regression tests.

The Cua monorepo publishes several components in one GitHub release feed. Looking at only the first 100 releases can stop finding Driver releases as other components publish. This change exhausts the paginated feed before choosing the highest eligible Driver version, with a 100-page bound and fail-closed handling of incomplete scans or malformed responses.

Unchanged

• pkgver=0.23.2 and the 24-hour quarantine.
• Both architectures, package dependencies, and bundled payload.
• The installer URL patch and pm.sh. They remain necessary until the pacman-aware upstream fix in fix(cua-driver): leave pacman-managed updates to pacman trycua/cua#3636 is released and reaches the package's normal update path.

Validation

• Bash syntax and whitespace checks pass.
• Added 37 deterministic fixture assertions to the existing bin/sync-upstream self-test entry point: later-page discovery, version ordering, stable-shaped prereleases, drafts/nightlies, quarantine boundaries, dates, checksums, and API failures.
• The local fixture run used GNU date and a mocked dotted-version comparator; it is not native pacman evidence. The repository's Arch CI must run the fixtures with real vercmp before this draft is ready.

GitHub has paused the upstream CI run for maintainer approval of this fork contribution: https://github.com/omacom/omarchy-pkgs/actions/runs/34168429328.

If #306 lands first, retarget this follow-up to master; it is not intended to replace the original package PR.