fix: Windows Ruby 3.1 Native Extensions Installs

[arielvalentin]

A change in ruby@3.1, rubygems, and/or bundler@2.3.23 is preventing native extensions both sqlite3 and nokogiri on Windows.

I tried a few different incantations to force bundler to load platform specific versions of x64-mingw-ucrt, however all attempts fell short in some way.

Locking the bundler version to 2.3.22 was the only way I could get the native extensions to install.

This is a temporary fix until we can figure out what changed in the bundler ecosystem to cause this issue.

cc: @johnnyshields

[johnnyshields]

@arielvalentin can you point me to the original test run that's failing and the error you are seeing? We did some Windows-related changes to Bundler in order to support Windows Ruby 3.1. Those changes should be entirely backwards compatible, so I'm surprised there are any issues here.

[johnnyshields]

@deivid-rodriguez

[arielvalentin]

@johnnyshields @deivid-rodriguez Here are some examples:

https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371768
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371805
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371859
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371939

[johnnyshields]

@arielvalentin I'm looking at the diff of ruby/rubygems@v3.3.22...v3.3.23

All my windows PRs were already released in v3.3.22 (which is the non-buggy version to which you've reverted) so I think the issue must be something unrelated to my changes.

This line in the diff looks suspect given the errors above:
ruby/rubygems@v3.3.22...v3.3.23#diff-1a57f160581a91a058c82b5d67dbba3cae6653a38529599911b0e4b0f0db9087R66

NoMethodError: undefined method `full_name' for nil:NilClass

  warning << "* #{unmet_spec_dependency}, depended upon #{spec.full_name}, unsatisfied by #{@specs.find {|s| s.name == unmet_spec_dependency.name && !unmet_spec_dependency.matches_spec?(s.spec) }.full_name}"

@deivid-rodriguez

[johnnyshields]

@arielvalentin recommend you to raise an issue with Rubygems.

[deivid-rodriguez]

Hi, it has already been raised several times, I kept this one opened: ruby/rubygems#5970. There's already a fix proposed at ruby/rubygems#5975. I recommend to stick to 2.3.22 until I release that.