[INT-209] Update CheckWithTech Slack message even if requestor doesn't have Slack linked

[markspolakovs]

This pull request includes updates to the handleSlackViewEvent and _sendCWTFollowUpAndUpdateMessage functions in the features/calendar/check_with_tech_actions.ts file to improve error handling and message updating logic.

Error handling improvements:

• Added a try-catch block around the Slack message update to log errors and ensure the requestor still receives a DM even if the update fails. [1] [2]

Message updating logic enhancements:

• Moved the logic for finding the requestor's Slack identity and sending a DM to the requestor to after the channel message update. [1] [2]
• Added new status checks for "Requested" and unknown statuses to ensure proper handling and logging of unexpected statuses.

Other small changes:

• Added a check for reqType not being "Note" before sending a follow-up message.
• Cleaned up the function by closing it properly.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.

Comments skipped due to low confidence (2)

features/calendar/check_with_tech_actions.ts:455

• The variable 'newContext' is declared but never used. This might be an oversight and should be removed or utilized.

let newContext;

features/calendar/check_with_tech_actions.ts:508

• [nitpick] The error message 'Failed to update #check-with-tech message' is too generic. Consider providing more context to help with debugging.

console.error("Failed to update #check-with-tech message");

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 suggestion.

Comments skipped due to low confidence (3)

features/calendar/check_with_tech_actions.ts:465

• [nitpick] The error message 'CWTFollowUp: Expected status other than Requested' could be more descriptive. Consider providing additional context or guidance.

case "Requested":

features/calendar/check_with_tech_actions.ts:467

• [nitpick] The error message 'CWTFollowUp: Unknown status ' + newStatus could be more descriptive. Consider providing additional context or guidance.

default:

features/calendar/check_with_tech_actions.ts:519

• The 'requestor' variable is being redefined after the try-catch block. Ensure this redefinition is intentional and doesn't cause any issues.

const requestor = cwt.submitted_by_user.identities.find(

[jenkins-ystv]

Deployed a preview of this PR to https://pr-193-internal.dev.ystv.co.uk