[rush-lib] Add async APIs for disk-touching methods in PackageJsonEditor, CommonVersionsConfiguration, and VersionPolicy

[Ian Clanton-Thuon (iclanton)]

Summary

Adds async variants of disk-touching methods across several rush-lib APIs and deprecates the corresponding synchronous methods. This is part of an ongoing effort to asyncify the Rush codebase to improve performance and avoid blocking the event loop.

Affected classes:

• PackageJsonEditor: adds loadAsync, saveIfModifiedAsync; deprecates load, saveIfModified
• CommonVersionsConfiguration: adds loadFromFileAsync, saveAsync; deprecates loadFromFile, save
• VersionPolicy: adds setDependenciesBeforePublishAsync, setDependenciesBeforeCommitAsync; deprecates setDependenciesBeforePublish, setDependenciesBeforeCommit

Also includes a constructor refactor for PackageJsonEditor that replaces pre-initialized empty Maps + forEach/.set() patterns with direct new Map(entries.map(...)) assignments, and replaces Object.prototype.hasOwnProperty.call(x, key) checks with Set.has() lookups.

Details

The sync methods are preserved with @deprecated JSDoc tags pointing to their async replacements to maintain backwards compatibility. The new async methods use JsonFile.loadAsync, JsonFile.saveAsync, and JsonFile.loadAndValidateAsync from @rushstack/node-core-library.

The VersionPolicy shared logic was extracted into two private helper functions (updateDependenciesBeforePublish, updateDependenciesBeforeCommit) to avoid duplicating the dependency-update traversal between sync and async variants.

How it was tested

Existing unit tests pass. The async paths follow the same logic as the tested sync paths and use the same underlying JsonFile async APIs used elsewhere in the codebase.