QVAC-16473 infra: add suite filtering and PR-triggered e2e test workflows for SDK

[lauripiisang]

🎯 What problem does this PR solve?

• SDK e2e tests (test-sdk.yml) could only be triggered manually with no suite filtering, no automated PR triggers, and no label-based control
• No way to run just the smoke suite (~84 tests, ~88s desktop) vs full suite (~388 tests) from the workflow dispatch UI
• Release branch PRs with SDK changes had no automatic e2e validation
• Android Device Farm test runs did not upload device logs as artifacts (iOS did)

📝 How does it solve it?

Suite filtering (test-sdk.yml + reusable workflows)

• Adds suite choice input to manual dispatch: full (default, no --suite flag), smoke (--suite smoke), custom (uses companion suite-custom string input)
• Adds exclude-suite string input for excluding tagged suites (e.g. slow,flaky)
• A resolve job maps the choice+custom pair to a plain string, then passes it through to all three reusable workflows (test-desktop-sdk.yml, test-android-sdk.yml, test-ios-sdk.yml)
• Reusable workflows append --suite / --exclude-suite flags to the qvac-test run:producer command

workflow_call support (test-sdk.yml)

• Adds workflow_call trigger with matching inputs (string types, same defaults) so other workflows can call it programmatically
• The resolve job handles both workflow_dispatch (choice → string) and workflow_call (string passthrough)

PR trigger workflow (on-pr-test-sdk.yml)

• Label-based: applying test-e2e-smoke runs smoke suite on all platforms; test-e2e-full runs full suite
• Release branch auto-trigger: PRs targeting release-* with packages/sdk/ changes automatically run full suite
• Authorization: uses the shared authorize-pr composite action with safe-to-test label gate for external fork PRs
• Success label: applies e2e-tested label to the PR when all tests pass
• Uses pull_request_target for secrets access (Device Farm, MQTT)
• Path filter packages/sdk/** gates opened/synchronize events; labeled events bypass path filter per GitHub behavior

Android Device Farm log uploads

• Added Device Farm artifact download and upload steps to test-android-sdk.yml cleanup job, mirroring the existing iOS implementation
• Waits for runs to complete, downloads Customer artifacts, uploads as device-farm-logs-android-* with 30-day retention
• Bumped cleanup job timeout from 5 to 10 minutes to accommodate log downloads

Other changes

• Default targets changed from desktop to all
• Updated desktop-platforms default to use mac-mini-m4-gpu (aligned with upstream rename)

🧪 How was it tested?

• test-sdk.yml manual dispatch can be tested on this branch with all suite/exclude-suite/filter combinations
• Limitation: on-pr-test-sdk.yml uses pull_request_target, which loads the workflow from the base branch — label triggers and release-branch auto-triggers can only be tested after merge to main. Post-merge verification:
  1. Open a test PR, apply test-e2e-smoke label, verify smoke suite runs on all platforms
  2. Apply test-e2e-full label, verify full suite runs
  3. Verify e2e-tested label is applied on success
  4. Open a PR targeting a release-* branch with SDK changes, verify auto-trigger
• Android Device Farm log upload can be verified on the next Android test run by checking for device-farm-logs-android-* artifact

[github-actions]

Tier-based Approval Status

**PR Tier:** TIER1

**Current Status:** ✅ APPROVED

**Requirements:**
- 1 Team Member approval ✅ (3/1)
- 1 Team Lead OR Management approval ✅ (1/1)



---
*This comment is automatically updated when reviews change.*

[lauripiisang]

/review

[lauripiisang]

/review