Release: Expose durable npm release phases

[ciampo]

Stacked on #80201. Follow-up workflow integration: #79906.

What?

Exposes the durable npm release lifecycle as prepare, publish, finalize, and all CLI phases.

Why?

The release workflow needs to run each durable phase in a separate fresh job while preserving the existing all-in-one command.

How?

• Adds the --phase option to the four npm release commands.
• Validates phase values and requires a prepared checkout for publish and finalize.
• Runs only the requested lifecycle step, with all remaining the default.

Testing Instructions

npm run test:unit -- tools/release/commands/test/common.js tools/release/commands/test/packages.js --runInBand
npm run lint:js -- tools/release/cli.js tools/release/commands/packages.js tools/release/commands/test/packages.js
npm run build

Testing Instructions for Keyboard

Not applicable; this changes release tooling only.

Screenshots or screencast

Not applicable.

Use of AI Tools

Codex was used to help split and verify the implementation and draft this description. I reviewed the resulting changes.

[github-actions]

Size Change: 0 B

Total Size: 7.72 MB

_{compressed-size-action}

[github-actions]

Flaky tests detected in 38b3e5d.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/29502134260
📝 Reported issues:

• [Flaky Test] should insert media, convert to blocks, and undo in one step #36123 in /test/e2e/specs/editor/blocks/classic.spec.js

[ciampo]

Closing for now since this PR is not getting much attention, but always happy to resume work at a later point in time.

(cc @jsnajdr )