chore: use locked version of cdk-generate-synthetic-examples

[mrgrain]

Reason for this change

The repository was using npx cdk-generate-synthetic-examples@latest which could lead to unexpected builds due to the latest version being used. This change locks the version to ensure reproducible builds. It also allows us to release changes to cdk-generate-synthetic-examples without having to worry much about the implications on this repo.

Description of changes

• Updated cdk-generate-synthetic-examples from ^0.2.32 to ^0.2.36 in package.json
• Added npm scripts rosetta and synthetic-examples to use locked versions via yarn
• Updated scripts/run-rosetta.sh to use yarn run instead of npx for both tools
• Removed init template upgrades from yarn-upgrade workflow (unrelated cleanup)
• Minor formatting fixes in yarn-upgrade workflow

This ensures all developers and CI use the same version of the synthetic examples generator, preventing potential inconsistencies.

Describe any new or updated permissions being added

No new permissions are added.

Description of how you validated changes

• Verified the scripts use the locked versions from package.json
• Confirmed yarn.lock contains the updated dependencies

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[mergify]

Merge Queue Status

✅ The pull request has been merged

This pull request spent 1 hour 30 minutes 29 seconds in the queue, including 45 minutes 25 seconds waiting for CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • chore: use locked version of cdk-generate-synthetic-examples #36242
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • chore: use locked version of cdk-generate-synthetic-examples #36242
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.