Add support for new Exception#detailed_message behaviour

Ruby 3.2 will introduce `Exception#detailed_message` and `did_you_mean`
has been already updated in Ruby 3.2 to use that.

The new behaviour means not changing the original `Exception#message`.
That means it is hard to get the previous error output, because
`Exception#detailed_message` includes not only `did_you_mean`
decorations, but also additional information like the exception class.

There's two cases where the did_you_mean message is displayed,
depending on whether we are in debug mode or not.

* In debug mode, we let the original exception be raised. In this case,
  I think it's fine to let the new wording blow up, so I just changed
  the assertions on the Exception raised to comply with the new
  behaviour.

* In non debug mode, we print a custom error. In this case, I slightly
  prefer the previous Thor output better than the one that
  `Exception#detailed_message` gives. The current one would be

  > Could not find command "paintz" in "barn" namespace.
  > Did you mean?  "paint"

  vs the new one

  > Could not find command "paintz" in "barn" namespace. (Thor::UndefinedCommandError)
  > Did you mean?  "paint"

So I changed `Thor::Base` to manually build the message so that we keep
the same error wording.

Author: deivid-rodriguez

lib/thor/base.rb

@@ -484,7 +484,16 @@ def start(given_args = ARGV, config = {})
         config[:shell] ||= Thor::Base.shell.new
         dispatch(nil, given_args.dup, nil, config)
       rescue Thor::Error => e
-        config[:debug] || ENV["THOR_DEBUG"] == "1" ? (raise e) : config[:shell].error(e.message)
+        if config[:debug] || ENV["THOR_DEBUG"] == "1"
+          raise e
+        else
+          message = e.message
+          extra_message = DidYouMean.formatter.message_for(e.corrections) if e.respond_to?(:corrections)
+          if extra_message
+            message << extra_message unless message.include?(extra_message)
+          end
+          config[:shell].error(message)
+        end
         exit(false) if exit_on_failure?
       rescue Errno::EPIPE
         # This happens if a thor command is piped to something like `head`,

spec/parser/options_spec.rb

@@ -114,10 +114,18 @@ def remaining
       parse("--bar", "baz", "--baz", "unknown")
 
       expected = "Unknown switches \"--baz\""
-      expected << "\nDid you mean?  \"--bar\"" if Thor::Correctable
 
       expect { check_unknown! }.to raise_error(Thor::UnknownArgumentError) do |error|
-        expect(error.to_s).to eq(expected)
+        expect(error.to_s).to include(expected)
+        break unless Thor::Correctable
+
+        extra_expected = "\nDid you mean?  \"--bar\""
+
+        if error.respond_to?(:detailed_message)
+          expect(error.detailed_message(highlight: false)).to include(extra_expected)
+        else
+          expect(error.to_s).to include(extra_expected)
+        end
       end
     end