`apify push --json` changed shape in 1.8.0 without a major bump

[janbuchar]

• apify push --json printed the raw build object until 1.7.x — top-level id, buildNumber, status. Since feat(push): add final status block and structured JSON output #1199 it prints an { ok, operation, actor, build } envelope. That shipped to stable in 1.8.0.
• apify/push-actor-action reads .id, .buildNumber and .status, so all three of its outputs are now null and it fails every successful push: https://github.com/janbuchar/menicka-crawler/actions/runs/32272220131/job/96136623842
• The CLI itself behaves correctly there — exit 0, ok: true, build tag applied. The red X is the action rejecting status: null. I'm fixing the action separately.
• Two things made this land quietly: it went out as a minor bump, and setup-apify-cli-action defaults to version: latest, so consumers got a new output format without opting into anything. --json is the machine-facing contract; it needs the same care as a function signature.
• Not a duplicate of apify push sometimes fail with RUNNING status #1150 — that one reported the same action error with status: RUNNING on 1.7.x, which was a genuine not-yet-terminal race.

[janbuchar]

This has been handled in the push-actor-action in apify/push-actor-action#25. The only concern is that we did a BC break without a major bump.