feat: add missing SocketMode options

[misscoded]

Summary

Adds missing SocketModeOptions to App init. Resolves #2292.

New options are made available as seen below:

/** Initialization */
const app = new App({
  token: process.env.SLACK_BOT_TOKEN,
  socketMode: true,
  appToken: process.env.SLACK_APP_TOKEN,
  logLevel: LogLevel.DEBUG,
  // New SocketModeOptions 
  socketModeOptions: {
    autoReconnectEnabled: true,
    clientPingTimeout: 420,
    pingPongLoggingEnabled: true,
    serverPingTimeout: 150,
  },
});

To test:

• Spin up TS-friendly Bolt project (https://github.com/slack-samples/bolt-ts-starter-template)
• Symlink @slack/bolt-js to this branch in project
• Verify that types exist
• Verify that changing these values reflects the same changes when logging the SocketMode receiver after initialization (i.e., autoReconnectEnabled, serverPingTimeoutMS, clientPingTimeoutMS, pingPongLoggingEnabled).

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.

[misscoded]

These all still exist, just made them alphabetical order bc it was driving me nuts 🫠 (but a sanity check is very welcome!).

[misscoded]

Same here. All still exist, just alphabetized.

[misscoded]

And again 😉 (alphabetized)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.46%. Comparing base (d6f9ce7) to head (ea3b4b8).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2735      +/-   ##
==========================================
+ Coverage   93.44%   93.46%   +0.01%     
==========================================
  Files          37       37              
  Lines        7675     7693      +18     
  Branches      669      669              
==========================================
+ Hits         7172     7190      +18     
  Misses        498      498              
  Partials        5        5              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mwbrooks]

🙇🏻 Nice, thanks for exposing these options through Bolt!

❓ I'll start to test the PR soon, but I was curious whether there's a reason why we don't organize the socket mode options into a separate object (there is probably a reason)? Something like:

/** Initialization */
const app = new App({
  token: process.env.SLACK_BOT_TOKEN,
  socketMode: true,
  appToken: process.env.SLACK_APP_TOKEN,
  logLevel: LogLevel.DEBUG,
  // New SocketModeOptions
  socketModeOptions: { 
    autoReconnectEnabled: true,
    clientPingTimeout: 42,
    pingPongLoggingEnabled: true,
    serverPingTimeout: 15,
  },
});

[WilliamBergamin]

Nice 💯
I also have the same question as @mwbrooks 🤔 having it in its own object could also help us with the separation of concern

[misscoded]

@mwbrooks @WilliamBergamin Bundled!

The caveat here is that SocketModeOptions (from the socket-mode pkg) requires appToken; we derive that from the root level initialization here. I've leveraged Omit to appease the type expectation, but open to alternatives (though it seems preferable at first blush to avoid the creation of a near-identical type).

[misscoded]

@mwbrooks @WilliamBergamin

❓ installerOptions is made public on the instance. I'm not sure why, exactly, but we can do the same for socketModeOptions if we think there's a use case for exposing it.

[zimeg]

📚 Quick question if the new options might be nice to reference from this page?

🔗 https://docs.slack.dev/tools/bolt-js/concepts/socket-mode