Add additional automation for issue generation on packages other than core controller packages

There are a variety of packages which are out of date on clients and causing issues. We should explore how we might add additional automation around these packages such that we can easily track and prioritize that work.

One idea was to change how the current automation works such that it monitors npm.

The issue does not name files, tests, or entry points. Start by reviewing the current automation for core controller packages and how it monitors npm, then determine which other packages and tracking signals must be covered. Done means there is an agreed automation design for detecting, tracking, and prioritizing outdated packages.

Written by the indexing model from the issue text.