Description of problem:

Updates to showcase plugin versions happens ad hoc when bumping BS versions and cherrypicking things to the release-1.y branches.

Expected results:

PRs (via GH action? custom renovate config?) are generated to suggest plugin version bumps (in yarn.lock / package.json / dynamic wrappers) at some interval ... daily? weekly? to ensure we are using / testing with the latest available compatible plugins

Caveat: if latest plugin sets a minium compatible BS version of 1.32, but we're generating a PR for the 1.3 branch, then we probably need to NOT update the plugin as it won't be compliant with BS 1.29.