Sync eng/common directory with azure-sdk-tools for PR 12734

[azure-sdk]

Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#12734 See eng/common workflow

[Copilot]

Pull Request Overview

This PR updates the cspell package configuration to use a scoped package name and pins the cspell dependency to an exact version. The changes improve dependency management by removing the version range specifier and making the package private.

Key changes:

• Renamed package from cspell-version-pin to @azure-tools/cspell
• Changed cspell dependency from ^9.2.1 to exact version 9.2.1
• Added "private": true to package.json

Reviewed Changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
eng/common/spelling/package.json	Updated package name to scoped @azure-tools/cspell, added private flag, and pinned cspell to exact version
eng/common/spelling/package-lock.json	Synchronized lockfile with package.json changes for name and version pinning

Files not reviewed (1)

• eng/common/spelling/package-lock.json: Language not supported

[Copilot]

The version field in package-lock.json should match the version in package.json. However, package.json no longer includes an explicit version field after adding "private": true. For private packages, it's recommended to either keep the version field in package.json for consistency or remove it from package-lock.json as well.

Suggested change

"version": "1.0.0",

[github-actions]

Hi @azure-sdk. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi @azure-sdk. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.