[rush] Prompt for package categorization for approvedPackagesPolicy #2648
Description
Summary
Developers tend to assume that the updates to browser-approved-packages.json are generated and that they should just blindly commit them, rather than checking to see if they are in the right category and updating appropriately. This tends to result in various build-time dependencies being categorized in the files as browser packages.
Since we already have inquirer in rush-lib for use by rush change, should we change rush update so that, if the policy is in effect and uncategorized packages are found, we prompt the user to categorize each new package as browser or nonbrowser?