fix: Correct Slack auth error formatting

[johnjcsmith]

No description provided.

[qodo-merge-pro]

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Validation Check Verify that integration.cluster_id is always defined and not null when this error handler is triggered to avoid potential undefined references in the error message text: `Sorry, I am having trouble authenticating you.\n\nPlease ensure your Inferable account has access to cluster <${env.APP_ORIGIN}/clusters/${integration.cluster_id}|${integration.cluster_id}>.`,

[qodo-merge-pro]

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
General	Add error logging to track authentication failures for better monitoring and debugging capabilities Add error logging to capture and track authentication failures, which will help with debugging and monitoring authentication issues. control-plane/src/modules/integrations/slack/index.ts [233-240] if (error instanceof AuthenticationError) { + console.error('Slack authentication error:', { error, userId: event.user, clusterId: integration.cluster_id }); client.chat.postMessage({ thread_ts: event.ts, channel: event.channel, text: `Sorry, I am having trouble authenticating you.\n\nPlease ensure your Inferable account has access to cluster <${env.APP_ORIGIN}/clusters/${integration.cluster_id}|${integration.cluster_id}>.`, }); return; } Apply this suggestion Suggestion importance[1-10]: 7 Why: Adding error logging is a valuable enhancement for production monitoring and debugging, especially for authentication failures which are critical to track. The suggestion provides useful context by including user ID and cluster ID in the log.	7