packge.json dep upgrade tool

MVP

• define schema / types for the metadata provided in basContributes
• Decide if to develop inside APP-Studio-Toolkit or in a new extension.
• Implement basic automatic upgrade flow with notification
  • exclude node_modules packages.
• expose setting to dis-able the upgrade flow
  • should it be enabled or disabled by default?

Open Questions / Issues

• to->from version numbers as semVer versions.
• grouping of notifications, is this possible?
• end of update notification, can this be done?
• VSCode and problems view for files not opened in the editor.
• Inspect the behavior of upgrade scenario with the limitation of the misalignment tools with package-lock files
• Distinction between general misalignment and upgrade scenario misalignment.

Bonus

• behavior on metadata conflicts.
• filter applying updates depending on the project type detected.

No implementation files or tests are named. Start by resolving whether the work belongs in APP-Studio-Toolkit or a new extension, then define the metadata schema for basContributes and scope the basic upgrade flow. Done means the agreed flow can notify about upgrades, excludes node_modules packages, and has a configurable setting.