Consider using `Exception#detailed_message` in our custom errors

[deivid-rodriguez]

Sometimes our custom errors wrap an underlying error and try to show the wrapped error and backtrace. See for example https://github.com/rubygems/rubygems/blob/c63c4b0305de7a5712436d37decca648b14b0091/bundler/lib/bundler/errors.rb#L134-L148.

@segiddins suggested that we may be able to use Exception#detailed_message to show the cause instead. I noticed that it's only available in newer rubies, but we could gradually move to that if it simplifies things. I also noticed there's Exception#full_message that includes the backtrace.

We should evaluate whether this makes sense for us and will simplify our errors, or whether we should not bother.

[NeimadTL]

Hi @deivid-rodriguez, @segiddins , is that something that needs to be tacked? if so and then if the first step is to move to newer rubies, how to do so please ? Thanks.

[deivid-rodriguez]

Hi @NeimadTL! It seems Exception#full_message is available at least since Ruby 3.1, so using that would not be a problem right now. Exception#detailed_message is only available since Ruby 3.2, so if we want to use that, we'd need to keep doing what we're doing on Ruby 3.1.

[NeimadTL]

Appreciate your feedback. Then, let's proceed with Exception#full_message. I'll raise a PR soon. In the mean time, could you assign me to this issue, thanks.