[rush] Expected that the rush update-autoinstaller command can sync the rush-plugins manifest.json files to the rush-plugins directory

Start with the implementation of rush update-autoinstaller --name rush-plugins and trace how it handles autoinstallers/rush-plugins/package.json and manifest files. Reproduce the command, then verify that each rush-plugin-manifest.json is copied into the rush-plugins directory and that the subsequent pnpm-lock.yaml update detects missing package files.

Summary

Currently, after running rush update-autoinstallers, the rush-plugin-manifest.json file is not copied to rush-plugins directory. Instead, it requires running rush update to trigger the sync of this file. This is somewhat counterintuitive in terms of usage.

Meanwhile, during development, it can also easily lead to the omission of the rush-plugin-manifest.json file. The development process is as follows:

1. Develop the plugin locally and declare it in autoinstallers/rush-plugins/package.json using link:./<path_to>/my-rush-plugin.
2. After testing is completed, the my-rush-plugin/rush-plugin-manifest.json file has already been saved in the git repository.
3. Assuming that the rush-plugin-manifest.json file is not declared in the files field of my-rush-plugin's package.json, it is difficult for CI to detect this issue at this point. This is because CI usually runs the install command, and only rush update can identify this problem.

If rush update-autoinstaller tried to copy the manifest files, than in the update pnpm-lock.yaml step, the problem will be detected.

Repro steps

Run rush update-autoinstaller --name rush-plugins

Expected result: The rush-plugin-manifest.json files will be copied to the rush-plugins directory.

Standard questions

Please answer these questions to help us investigate your issue more quickly: