* Merge RubyGems-3.4.7 and Bundler-2.4.7

* Merge RubyGems-3.4.8 and Bundler-2.4.8

* Skip failing test on MSWin

* Merge RubyGems-3.4.9 and Bundler-2.4.9

* Merge RubyGems-3.4.10 and Bundler-2.4.10

---------

Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>

Dependabot bumped the repo's configuration in 0c996fa but it did not
bump the version in the template for `bundler gem`

https://github.com/rubygems/rubygems/commit/e14980e169

https://github.com/rubygems/rubygems/commit/8836fe157b

Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>

https://github.com/rubygems/rubygems/commit/3260173c59

https://github.com/rubygems/rubygems/commit/f5bead5634

This change avoids a YAML Float-to-String conversion, which turns a 3.0 into a "3". That can make names of builds less clear.

In order to use this new capability, I added a "name" descriptor to the matrix-created Job.

https://github.com/rubygems/rubygems/commit/6221241ad4

ref: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags

Running jobs with only branch name, without `branches:`, CI fails

https://github.com/rubygems/rubygems/commit/fcec167d61

Even if it only has one entry at the moment, it makes it easier to add
new entries by doing it this way.

https://github.com/rubygems/rubygems/commit/46232fe265

Co-authored-by: NeimadTL <damientalbot26@gmail.com>

Otherwise CI will run once for every pull request update and once for
every push.

The disavantage is that people working on a non default branch without
creating pull requests won't get CI run at all.

I think the advantages are greater than the disadvantages, it's also my
personal workflow, and it's something desired enough so that someone
opened an issue about it.

So let's do it!

https://github.com/rubygems/rubygems/commit/924d916a73

Co-authored-by: NeimadTL <damientalbot26@gmail.com>