fix(scripts): use packageManager field for yarn version

[trivikr]

Issue

Changeset users npm for publishing

When we attempted to use node 24 for publish step in #1006, the GitHub Action failed because of devEngines

🦋  info npm info aws-sdk-js-codemod
🦋  error Received an unknown error code: EBADDEVENGINES for npm info "aws-sdk-js-codemod"
🦋  error The developer of this package has specified the following through devEngines
🦋  error Invalid engine "packageManager"
🦋  error Invalid name "yarn" does not match "npm" for "packageManager"
🦋  error [object Object]

https://github.com/aws/aws-sdk-js-codemod/actions/runs/16817222460/job/47636819313

Description

Switches to using packageManager field for yarn version

$ yarn set version 4.9.2 

Although devEngines is implemented by corepack, yarn continues to use packageManager field.
And as per Yarn Discord, it'll introduce it's own version manager soon.

Testing

Publish will be tested post merge

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e7e6592

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.