fix(live): use gems for the default Ruby version

[imobachgs]

Use rubygem(foo) instead of ruby3.X-rubygem-foo to use the gems for the project's default Ruby version.

Warning

Not tested yet!

[mvidner]

IIRC, we used to do this in YaST, just using whatever Ruby-version of gems that is available, but then people were reporting bugs downstream in the build process, when we got the dependencies seemingly satisfied while in fact they were mismatched.

Ideally we are pinning the version dynamically like this, but in a KIWI XML file that may not be possible

RUBY_VERSION=$(ruby -e "puts RbConfig::CONFIG['ruby_version']")
zypper --non-interactive install ... "rubygem(ruby:$RUBY_VERSION:yast-rake)" ...

agama/.github/workflows/weblate-update-pot.yml

Lines 31 to 32 in 83ef39c

	RUBY_VERSION=$(ruby -e "puts RbConfig::CONFIG['ruby_version']")
	zypper --non-interactive install --no-recommends diffutils git gettext-tools npm-default "rubygem(ruby:$RUBY_VERSION:yast-rake)" "rubygem(ruby:$RUBY_VERSION:gettext)" yast2-devtools which

[imobachgs]

According to @mchf findings, it seems to work.

[mchf]

I did something similar to what is in this PR here: 75b2715 and was able to build the iso locally. So, this one LGTM as far as deleting those references with ruby3.2-rubygem in some sub-products without further replacement is fine.

[mchf]

As commented. LGTM