[Tooling] Update Ruby gems

[AliSoftware]

Update gems to latest version (by just running bundle update), especially to fix a security issue with nokogiri

As long as CI is green we should be good to go.

Ref: AINFRA-122

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21825-32dddde
	Commit	32dddde
	Direct Download	wordpress-prototype-build-pr21825-32dddde.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21825-32dddde
	Commit	32dddde
	Direct Download	jetpack-prototype-build-pr21825-32dddde.apk

Note: Google Login is not supported on these builds.

[twstokes]

LGTM. Any stability concerns @AliSoftware about packages that had major version updates? (e.g. activesupport)

[AliSoftware]

LGTM. Any stability concerns @AliSoftware about packages that had major version updates? (e.g. activesupport)

Good catch and good question.
I'm surprised the dependency to activesupport is not bound to a SemVer constraint (~> x.y) but open-ended instead btw.

From a quick look at the changelog between last 7.x version and 8.0.0, I didn't see any breaking change during the bump to 8.x that should impact my knowledge of what we use of that lib in our codebase.
But activesupport is a pretty big libraries with lots of methods so it's hard to be sure (and we probably use less than 1% of them… if any, actually?). So I'd say worst case scenario something breaks or crashes during one of our automation lanes because of a breaking change in an activesupport Ruby method and we fix it when we discover it anyway.