chore(ci): add dry-run mode to release workflow

[lukascivil]

Objective

Allow previewing the release workflow (versioning/publishing) without producing side effects — no tag update, no npm publish, and no S3 deploy — so release changes can be validated safely before a real run.

What was done

• Added a dry_run boolean input to the release-and-publish workflow in .github/workflows/release-and-publish.yml (defaults to false).
• Routed the Version And Publishment step to yarn release:dry-run when dry_run is true, otherwise the existing yarn release.
• Guarded the Tag last-release step and the Deploy Json Difference to Amazon S3 step with if: github.event.inputs.dry_run != 'true' so they are skipped during a dry run.
• Added the release:dry-run script in package.json, which forwards --dry-run to yarn nx run-many --target=version --parallel=1.
• Removed the long-dead .github/workflows/npm-publish-github-packages.yml file (entire contents were commented out).

Test plan

• From the GitHub Actions UI, run release-and-publish with dry_run=true and name=all; confirm versioning runs but no tag is updated, no package is published, and no S3 deploy step executes.
• Run the same workflow with dry_run=false (or unchecked) on a test branch and confirm the existing behavior (tag, publish, S3 deploy) is unchanged.
• Run yarn release:dry-run --all locally and verify it invokes nx run-many --target=version --parallel=1 --dry-run without writing changes.