Implement auto_acknowledge feature for socket clients.

[amshamah419]

Summary

The goal is to allow the Socket Mode Client to automatically send the acknowledgment notification to reduce the likelihood that a message could expire while waiting in the event queue.

The default is currently False to prevent any backwards compatibility issues.

fixes: #1299

Category (place an x in each of the [ ])

• slack_sdk.web.WebClient (sync/async) (Web API client)
• slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
• slack_sdk.socket_mode (Socket Mode client)
• slack_sdk.signature (Request Signature Verifier)
• slack_sdk.oauth (OAuth Flow Utilities)
• slack_sdk.models (UI component builders)
• slack_sdk.scim (SCIM API client)
• slack_sdk.audit_logs (Audit Logs API client)
• slack_sdk.rtm_v2 (RTM client)
• /docs-src (Documents, have you run ./scripts/docs.sh?)
• /docs-src-v2 (Documents, have you run ./scripts/docs-v2.sh?)
• /tutorial (PythOnBoardingBot tutorial)
• tests/integration_tests (Automated tests for this library)

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've run python3 -m venv .venv && source .venv/bin/activate && ./scripts/run_validation.sh after making the changes.

[CLAassistant]

All committers have signed the CLA.

[seratch]

Hi @amshamah419, thanks for sending this! But for the reasons that I mentioned at #1299 (comment), we would like to hold off working on the details of this PR at this moment.

[seratch]

Thanks again for sending this PR! but for the reason I mentioned above, we are not planning to add this flag at least in the short term. So, let us close this issue now. It'd be appreciated if you could understand this.