loose plugin dependencies permit incompatible versions

Overview: UI applications with loose * dependencies on plugins pull incompatible versions into the build. The same problem bit us when we published Iris hotfixes after Juniper was released. Here, we see it with Lotus hotfixes now that Morning Glory versions are available.
Steps to Reproduce:

1. Checkout platform-complete#R1-2022 and run yarn install

Expected Results: Only R1-2022 versions are present in the build, as specified in package.json:

• "@folio/plugin-find-contact": "3.1.1",
• "@folio/plugin-find-fund": "1.0.0",
• "@folio/plugin-find-instance": "6.1.6",
• "@folio/plugin-find-interface": "3.1.1",
• "@folio/plugin-find-organization": "3.1.1",
• "@folio/plugin-find-po-line": "3.1.1",
• "@folio/plugin-find-user": "6.1.0",

Actual Results: Multiple versions of some dependencies are present in the build, including some that are from R2-2022 and rely on versions of stripes-acq-components that are not present in the R1-2022 release:

• "@folio/plugin-find-contact": "3.2.0",
• "@folio/plugin-find-fund": "1.1.0",
• "@folio/plugin-find-instance": "6.2.0",
• "@folio/plugin-find-interface": "3.2.0",
• "@folio/plugin-find-organization": "3.2.0",
• "@folio/plugin-find-po-line": "3.2.0",
• "@folio/plugin-find-user": "6.2.0",

Interested parties: dennisbridges, sduvvuri