Make release publishing explicit and retry-safe

[TDanks2000]

Root cause

After the generated 1.1.0 version PR was merged, the combined changesets/action publish path failed before creating the npm tag or GitHub release. This left main correctly versioned at 1.1.0 but unpublished.

Fix

• Detect whether pending Changesets remain.
• Use Changesets only for version-PR generation.
• Publish an already-versioned package with an explicit npm publish --provenance step.
• Check npm first so reruns do not attempt to republish an existing version.
• Create the matching GitHub release explicitly and idempotently.
• Retain the pinned npm 11.18.0 Trusted Publishing toolchain.

Result

Merging this PR runs the explicit publish path for 1.1.0 and creates v1.1.0 after npm succeeds.