ci: bound inherited automation and validation cost

[Guitaraholic]

Human comments

What was wrong

Inherited daily iOS tests and nightly package/desktop/mobile publishing could start costly work without a DataHaze development change. The full validation suite also ran again after merge, and two tiny version checks each requested a paid runner.

What changed

• Remove inherited automatic mobile E2E and publishing schedules and the daily upstream marketplace live check; retain explicit manual and release functionality.
• Run ordinary validation on pull requests and manual dispatch, cancel obsolete PR work, and skip paid jobs on drafts. ready_for_review runs the unchanged PR suite. CI required explicitly fails drafts or missing/failed applicable jobs; skipped tests cannot produce a green aggregate.
• Combine the two version checks into one bounded GitHub Linux job with cancellation, avoiding duplicate branch-push checks.
• Keep existing mobile, desktop, EAS, deploy and release job limits and release serialization. Manual full compatibility validation remains available.

How you verified

• actionlint v1.7.7 passed for all changed workflows with existing Blacksmith runner labels registered.
• Both version scripts passed locally.
• Seven aggregate-gate scenarios passed: successful PR, draft rejection, failed/cancelled/skipped prerequisites, missing manual compatibility, and successful manual compatibility.
• YAML assertions confirmed no automatic schedules in the changed inherited workflows, no duplicate main-push validation, and draft gating of every paid PR job.

This PR stays draft to avoid starting the inherited paid validation matrix. No mobile, publishing, release, EAS or Blacksmith jobs were dispatched. Full product validation was not run; making this PR ready will request the existing paid nine-job suite.

AGENT GENERATED