Remove custon `job_status` ouput in favor of the native `needs.<job_id>.result`

In the build-plugin-zip.yml workflow, a custom job_status output is defined for use in later jobs.

GitHub Actions has native support for this information through needs.<job_id>.result. This should be used instead of a custom output to avoid unintentionally introducing an insecure pattern or bug.

It's possible that there are other similar instances within workflow files, but Claude did not find any when I asked it to perform an analysis.

I audited the remaining outputs: blocks in the workflow directory. None of them are redundant reimplementations of native context:

Workflow	Job	Output	Why it's legitimate
build-plugin-zip.yml	compute-stable-branches	current_stable_branch, next_stable_branch	Computed from GitHub Releases API
build-plugin-zip.yml	bump-version	old_version, new_version, release_branch, release_branch_commit, trunk_commit	Custom semver/commit data
end2end-test.yml	merge-artifacts	has-flaky-test-report	Derived from steps.*.outputs.artifact-id presence
unit-test.yml	compute-previous-wordpress-version	previous-wordpress-version	Computed from WP.org API
upload-release-to-plugin-repo.yml	compute-should-update-trunk	should_update_trunk	Computed from WP.org plugin API
upload-release-to-plugin-repo.yml	get-release-branch	release_branch	Derived from tag name

I also grepped for any other use of job.status or job. being exposed via outputs — build-plugin-zip.yml is the only occurrence.