(CDPE-7204) Update to Ruby 3.2, PDK 3.4.0, and Debian bullseye and update tooling gems

[Magisus]

This commit updates PDK to current latest, 3.4.0. It also removes some
unnecessary rm lines from the Dockerfile: in PDK 3.2.0 the
dependencies that used to be used to analytics were dropped when the
analytics code was removed, and this included the httpclient gem,
which contained the files we used to delete because they triggered
security scanners. The gem is no longer included with the PDK package,
so the delete lines aren't needed.

Building this image with the latest nokogiri (1.18.8) ran into an issue
where they have split their gem platforms for the precompiled gem from
just linux to linux-gnu and linux-musl. However on Ruby 3.1 and
Debian Buster, bundler recognized the platform as just plain linux, so
it failed to grab the precompiled gems. We wanted to update to Ruby 3.2
to match what puppet-agent ships with anyway, and the docker images for
3.2 only support back through bullseye, not buster, so this commit
also updates to Debian Buster and Ruby 3.2. On this platform, bundler
correctly detects the gem platform and installs the correct pre-compiled
gems.

Updating to Ruby 3.2 required installing a newer version of rugged (a
dependency of octocatalog-diff), and this version depends on
pkg-config, as well as libssl-dev rather than just libssl1.1 for
HTTPS support, so this commit also installs those.

This PR also updates all of the other test gems and their deps. See commits for details.

[Magisus]

Older versions of bundler have some weird bugs around the gem platform stuff. Just updating this to latest didn't fix the issue I was seeing with nokogiri, but it also didn't hurt anything, so figured I might as well update it.

[Magisus]

Release note for nokogiri explaining the gem platform change: https://nokogiri.org/CHANGELOG.html#v1180-2024-12-25 Note that even rebuilding the puppet8 tag with the existing deps would hit this, since we always try to pull latest nokogiri right now. Even on new versions of bundler, and even trying to add the bundle lock --add-platform, I was not able to get Ruby 3.1+buster to register as x86_64-linux-gnu, which meant the install was falling back to the case described in the second paragraph, which failed trying to extract the bundled libraries they ship. Adding the xz-utils package (as described here) fixed that, but I figured since we wanted to bump Ruby anyway, I'd try that, and that fixed it the better way.

[Magisus]

I've tested this with all of our built-in jobs and they all succeeded. But I'm not sure how useful the code I tested them on was.

[Magisus]

This currently pulls in puppet 8.10, which was the last gem release, but the latest puppet version is actually 8.12. I think this is probably related to the Puppet Core changes, I imagine they stopped shipping gems to Rubygems. I'm going to figure out what it would take for us to get the actual latest version of Puppet here.

[Magisus]

Getting a more recent gem than 8.10 is going to be a bit fraught, and might have security implications for the way we build and publish this image. For now, I might leave that for a separate effort while we discuss how to make it work. It seems like it might be valuable to get the rest of these changes published sooner rather than later.