Add generated TUS protocol contract canary

[kvz]

Experimental Status

Experimental work: this PR is part of an exploratory contract/generated docs and SDK effort, and is intentionally kept as a Draft while the approach is validated.

Why: this is the Android companion canary for the API2 contract generator work. tus-android-client delegates wire-level TUS behavior to tus-java-client, so this PR keeps protocol truth generated while proving the Android-specific resume-storage primitive is still covered.

What changed:

• add a generated test-side TUS protocol/feature fixture from API2 contracts
• add a Robolectric test that consumes the generated singleUploadLifecycle feature and verifies TusPreferencesURLStore satisfies the generated store-resume-url primitive
• tidy the CI trigger block by removing a misplaced runs-on, adding ready_for_review, and enabling manual workflow_dispatch

Validation:

• api2/bin/cli.ts contracts tus-sdks --no-motd --platform android --sdk-root ../tus-android-client --compare-existing
• Local ./gradlew clean check --no-daemon is blocked on this workstation by missing Android SDK configuration (ANDROID_HOME/local.properties), so CI should be the Android build authority here.

Companion PRs (tus org only)

• tus-js-client: Mark protocol versions as generated tus-js-client#872
• tus-go-client: Add generated TUS protocol canary tus-go-client#6
• tus-py-client: Add generated TUS protocol canary tus-py-client#114
• tus-java-client: Add generated TUS protocol contract canary tus-java-client#149

Notes

GHA note: PR events are present and the repo workflows are active, but GitHub Actions has not created pull_request suites for this human-authored branch. The branch adds workflow_dispatch/ready_for_review coverage where applicable; local generator checks remain the current validation signal.