Explicitly require did_you_mean in Bundler::CLI::Common#gem_not_found_message

Since error enhancer gems are now lazy-loaded, did_you_mean is not
available until the first exception display. Bundler uses
DidYouMean::SpellChecker directly, so it needs to require the gem
explicitly.

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

Author: hsbt

lib/bundler/cli/common.rb

@@ -98,7 +98,8 @@ def self.gem_not_found_message(missing_gem_name, alternatives)
       alternate_names = alternatives.map {|a| a.respond_to?(:name) ? a.name : a }
       if alternate_names.include?(missing_gem_name.downcase)
         message += "\nDid you mean '#{missing_gem_name.downcase}'?"
-      elsif defined?(DidYouMean::SpellChecker)
+      else
+        require "did_you_mean"
         suggestions = DidYouMean::SpellChecker.new(dictionary: alternate_names).correct(missing_gem_name)
         message += "\nDid you mean #{word_list(suggestions)}?" unless suggestions.empty?
       end