Currently, the automatic discovery and update of plugins workflow rely on `npm search` to retrieve the list of published plugins based on a list of package name regexes.

This would work well if `npm search` would return robust and consistent results, but it happens that it is not the case: sometimes some packages are missing, sometimes only the frontend or the backend is returned in the package list.

This is very error-prone. If a package, which has been published more recently that its sibling, is missing, it can even even lead to a situation when the workflows opens a PR to propose an older commit (and a truncated `plugins-list.yaml` content.

We have to:

• not depend on nom view in this workflow
• still have a way to fill a list of packages we want to watch for automatic discovery.

Here is a proposed approach:

• Have a list of packages we want to integrate in the overlay and monitor for automatic commit updates, committed in the overlay repo (o which branch is still TBD)
• Have a regular workflow that proposes PR to complete this list (only adding elements to it, never removing them, so we can use `npm view` and the regexes here)
• Have the `UpdatePluginRepoRefs` use the stored list.

Alternate approaches could probably be taken according to the directions taken in implementing issue https://issues.redhat.com/browse/RHIDP-7068