Enable the logging of the request body

[ts-3156]

When debugging, I sometimes want to see the request body. I don't know if other people feel the same way. If you don't need it, please feel free to close this pull request.

[dangerpr-bot]

	2 Warnings
⚠️	There're library changes, but not tests. That's OK as long as you're refactoring existing code.
⚠️	Unless you're refactoring existing code or improving documentation, please update CHANGELOG.md.

Here's an example of a CHANGELOG.md entry:

* [#374](https://github.com/slack-ruby/slack-ruby-client/pull/374): Enable the logging of the request body - [@ts-3156](https://github.com/ts-3156).

Generated by 🚫 Danger

[dblock]

I think we don't want this by default. Did you figure out a way to do this in your own code? I would like us to document how to do this without changing the default configuration, in README.

[ts-3156]

@dblock Thank you for taking the time to reply.

I think we don't want this by default.

I have the same opinion. However, I have not come up with a suitable code to pass a value for bodies: true via Slack.configure.

Slack.configure do |config|
  config.log_bodies = true # <- This name feels strange.
end

Did you figure out a way to do this in your own code?

Yes. I found this option when I investigated strange behavior that Slack doesn't display the image preview correctly.

I would like us to document how to do this without changing the default configuration, in README.

If you need this option for logging, I will write how to do it in README. However, in order to use this option, I need to modify not just the documentation, but also the code. Is this really what you want?

You don't need to hurry. It is OK if this idea is discarded.

[dblock]

How about introducing logger_options?

If you feel more ambitious, take a look at https://lostisland.github.io/faraday/middleware/logger. It also supports blocks and filtering which we could expose. The https://github.com/ashkan18/graphlient gem does it like so:

 Graphlient::Client.new('http://test-graphql.biz/graphql') do |client|
      client.http do |h|
        h.connection do |c|
          c.adapter Faraday::Adapter::Rack, app
        end
      end
    end

So http and connection yield from within the configuration and you would want to be able to write the following, overriding the :logger part of the configuration.

 Slack.configure do |config|
   config.connection do |conn|
     conn.response :logger, logger, { bodies: true }
   end
 end
end

[dblock]

AI posting on behalf of @dblock: thank you for the proposal. The request callback API merged in #605 now makes request-body debugging opt-in without enabling body logging for every client:

debug_client = client.with_request do |request|
  logger.debug { "Slack request body: #{request.body.inspect}" }
end

debug_client.chat_postMessage(channel: channel, text: text)

This returns a configured client copy, leaves the original unchanged, and runs on each HTTP call, including pagination. The callback sees the body before adapter encoding—typically a parameter hash rather than the final encoded wire payload—so it is useful for debugging submitted arguments, not an exact replacement for wire-level logging. Redact sensitive values and avoid logging tokens, private message text, or file contents indiscriminately.

Closing this global-logging change in favor of the opt-in callback approach.