Point the Ruby::Box guards at their tracker issues

Both guards were written before the bugs had tickets. The $VERBOSE one
is now [Bug #22282] rather than a relative of [Bug #21867], and the
RUBYOPT -r one is [Bug #22295] rather than unreported.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: hsbt

spec/commands/install_spec.rb

@@ -2063,8 +2063,8 @@ def run
   end
 
   it "preserves bundled native extensions when BUNDLE_CLEAN removes another gem" do
-    # The command-line/RUBYOPT -r bypasses gem activation under RUBY_BOX=1, a
-    # ruby-core bug (unreported, related to [Bug #21760] item 3)
+    # The command-line/RUBYOPT -r bypasses gem activation under RUBY_BOX=1
+    # (https://bugs.ruby-lang.org/issues/22295)
     skip "-r cannot activate gems under Ruby::Box" if defined?(Ruby::Box) && Ruby::Box.enabled?
 
     build_repo4 do

test/rubygems/test_gem_package_tar_header_ractor.rb

@@ -10,7 +10,7 @@
 class TestGemPackageTarHeaderRactor < Gem::Package::TarTestCase
   def setup
     super
-    pend "Ruby::Box ignores $VERBOSE=, so assert_ractor cannot keep the Ractor experimental warning out of the child stderr (ruby-core bug, same family as https://bugs.ruby-lang.org/issues/21867)" if ruby_box_enabled?
+    pend "Ruby::Box ignores $VERBOSE=, so assert_ractor cannot keep the Ractor experimental warning out of the child stderr (https://bugs.ruby-lang.org/issues/22282)" if ruby_box_enabled?
   end
 
   SETUP = <<~RUBY