refactor: replace custom qa runner with cali

[thymikee]

Summary

Replace the bespoke QA agent implementation with cali@0.4.0-0 and keep the EAS workflow integration slim.

• swap the custom AI SDK runner for cali qa
• generate a cali-context.json in the workflow wrapper and export PR comment outputs from the resulting report
• remove obsolete custom runner files and the extra iOS provisioning layer that cali now handles
• trim package dependencies and document the new flow

Validation

• npm install
• ./node_modules/.bin/cali qa --help
• npm run lint
• bash -n ./scripts/agent-qa/run-and-export.sh
• bash -n ./scripts/agent-qa/provision-android-emulator.sh
• node /Users/thymikee/.agents/skills/expo-cicd-workflows/scripts/validate.js .eas/workflows/agent-qa-mobile.yml

[expo]

Agent QA comment was not produced.

[FiberJW]

Hi! Just chiming in since GitHub notified me that GitHub app installation access tokens are showing up on this PR. I can see it here: JSON report > context > repository > provider/cloneUrl.

Can we strip out that info or redact that URL? It contains a short-lived installation access token that's primarily intended for secure execution environments (EAS servers) and shouldn't be published publicly (and, if so, will be immediately invalidated by GitHub).

Thanks!

[thymikee]

Thanks for flagging that @FiberJW! addressed