actions: various pnpm publishing flow fixes

[alexhancock]

Fixes four things with the in progress pnpm based publishing flow for the new TUI

• Bumps node and pnpm versions - as required https://github.com/block/goose/actions/runs/23541679693/job/68536905108
• Do not run Publish to npm on irrelevant main pushes
• Remove the environment gate on the Publish to npm workflow for the time being, so we can let the job run. Publishing will still not be able to occur, as the NPM_PUBLISH_TOKEN is only available on main
• Syntax on multi-line quoted things

All syntax now passes actionlint, and we will be able to run the full job (minus the part that actually does a working publish) on branches now

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 22a557e688

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Expand push path filters to include all publishable packages

The new on.push.paths filter only matches crates/goose-acp/**, ui/acp/**, and workflow files, so pushes to main that change other published workspace packages (for example ui/text/** or ui/goose-acp-server/**) will no longer trigger this release workflow. Since this workflow still builds ui/text and runs changeset publish from ui, those package updates can be skipped indefinitely unless someone manually dispatches the workflow.

Useful? React with 👍 / 👎.