Do not support ruby 3.2

[Lucas Kanashiro]

ruby-nokogumbo/2.0.5-1build2 FTBFS with Ruby 3.2. Upstream archived the Github repository and stated that ruby 3.2 will not be supported and users of the gem should now use ruby-nokogiri:

https://github.com/rubys/nokogumbo/#readme

This is enough reason for us to remove the package from Noble, where ruby 3.2 will be the default.

However, it has one reverse build dependency:

$ reverse-depends src:ruby-nokogumbo
$ reverse-depends src:ruby-nokogumbo -a source
Reverse-Build-Depends
=====================
* ruby-premailer (for ruby-nokogumbo)

ruby-premailer latest upstream version do not depend on ruby-nokogumbo and already uses ruby-nokogiri. I uploaded ruby-premailer to version 1.22.0-1 in Debian unstable and should be sync'ed soon into Noble, once it lands in the archive we can remove ruby-nokogumbo (source and binary) from Noble.

[Christian Ehrhardt  (paelzer)]

FYI: Looks fine on a first check, but ruby-premailer | 1.22.0-1 hasn't made it over to noble yet.

[Lucas Kanashiro (lucaskanashiro)]

ruby-premailer/1.22.0-1 already landed in the release pocket. ruby-nokogumbo can be removed now.

[Christian Ehrhardt  (paelzer)]

Indeed, dependencies are gone now.

The case was good before other than that and AFAICS nothing changed.
ruby-nokogumbo is not in -proposed with a fix yet, in noble we only have

 ruby-nokogumbo | 2.0.5-1build2 | noble/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x

Removing packages from noble:
 ruby-nokogumbo 2.0.5-1build2 in noble
  ruby-nokogumbo 2.0.5-1build2 in noble amd64
  ruby-nokogumbo 2.0.5-1build2 in noble arm64
  ruby-nokogumbo 2.0.5-1build2 in noble armhf
  ruby-nokogumbo 2.0.5-1build2 in noble ppc64el
  ruby-nokogumbo 2.0.5-1build2 in noble riscv64
  ruby-nokogumbo 2.0.5-1build2 in noble s390x
Comment: not compatible with ruby 3.2 (LP: #2052737)
Remove [y|N]? y
1 package successfully removed.