Improve version bump flexibility and automate AWS and sequel deps to minor updates

[alexcams]

• enhancement

Release notes

[rn:skip]

What does this PR do?

Automate AWS and sequel minor bump on lock file patch bumps and adds a config parameter to version bump workflow to improve its flexibility.

Why is it important/What is the impact to the user?

It allows to select gems where a desired feature/fix has been shipped as minor release and also keeps up to date gemps that don't ship patch releases.

Related issues

• Relates #7160

Tests

Example job run and PR created with multi_json as minor selected gem and public_suffix as major. AWS and sequel also downgraded manually to see them automatically updated to last minor.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

[donoghuc]

As we discussed in person, lets extend this pattern (identify gems for which we explicitly want to include minor versions for by default in a whitelist) to 9.x. Looks like we might be best off with targetting at main then backporting to all active branches (and updating defaults as needed in the backport PRs).

I'm cool with starting off with dynamically generating the whitelist (for example ./vendor/jruby/bin/jruby -S bundle list --name-only | grep '^aws-') we should keep an eye on this and make sure it is complete over the course of a few runs (IE no false positive/negative). We can always manage a static list down the road if we find it to be too complex to dynamically generate it.