Currently when we get the error message we get no details of what went wrong unless we get the response_metadata for the error which is not intuitive as most people when they get an error and print the exception they would expect to see as much details as possible.
Additionally updated ruby-version in the project to be the latest as most people would be using that one as their default, though not changing the one required by the gem
fixes: https://github.com/slack-ruby/slack-ruby-client/issues/482
Currently when we get the error message we get no details of what went wrong unless we get the response_metadata for the error which is not intuitive as most people when they get an error and print the exception they would expect to see as much details as possible.
Additionally updated ruby-version in the project to be the latest as most people would be using that one as their default, though not changing the one required by the gem