Update bundler to 2.4.22

[schneems]

Prior #1426
Closing #1408

[schneems]

Breaking change (that seems undocumented, so I'm not sure if it's intentional or not).

$ cat Gemfile
source "https://rubygems.org"

ruby "~> 3.0.0"

gem "rake"
$ cat Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    rake (13.0.6)

PLATFORMS
  ruby
  x86_64-darwin-20

DEPENDENCIES
  rake

BUNDLED WITH
   2.3.7
$ bundle _2.3.27_ platform --ruby
ruby 3.0.0
$ bundle _2.4.22_ platform --ruby
No ruby version specified

Also 2.4.x dropped support for Ruby 2.5: https://github.com/rubygems/rubygems/blob/3fbb8bb93cf54b14374825859541a522c43a8377/bundler/CHANGELOG.md#breaking-changes-1

I need to investigate if it's a policy change and simply untested or if it hard breaks (uses newer APIs etc.) I'm guessing it uses newer APIs.

I would like to not break my customers on Ruby 2.5. So I'll need to think on another strategy. Possibly multiple versions of "blessed" bundler versions like 2.2, 2.3, 2.4, 2.5 etc.

Again, in the long term I want to get out of this managed bundler version game, but I don't have that luxury in the short term.