chore: Move chatbot handlers to Lambda [CHI-3218]

[GPaoloni]

This PR is related to techmatters/serverless#757 and https://github.com/techmatters/infrastructure-config/compare/master...gian_CHI-3218.

Description

This PR migrates all the chatbot handlers to the account scoped Twilio Lambda.

• Exposes 3 new endpoints, analogous to those from Serverless
  • captureChannelWithBot (/lambda/twilio/account-scoped/{accountSid}/channelCapture/captureChannelWithBot).
  • chatbotCallback (/lambda/twilio/account-scoped/{accountSid}/channelCapture/chatbotCallback).
  • chatbotCallbackCleanup (/lambda/twilio/account-scoped/{accountSid}/channelCapture/chatbotCallbackCleanup).
• Adds postSurveyListener, a taskrouter event listener to trigger post survey.

Migration

To Lex v2 migration, refer to techmatters/serverless#756.

• Ensure https://github.com/techmatters/infrastructure-config/pull/440 is applied in the target environment.
• Change Studio flow
  • Create a new Make HTTP Request widget with the following configuration:
    • Name: captureChannelWithBot.
    • Method: POST.
    • URL: <hrm base url>/lambda/twilio/account-scoped/{%if trigger.conversation%}{{trigger.conversation.AccountSid}}{%else%}{{trigger.message.AccountSid}}{%endif%}/channelCapture/captureChannelWithBot.
    • Content type: Application/JSON.
    • Request body:

        {
          "channelSid": "{{flow.channel.address}}",
          "message": "Incoming webchat contact",
          "studioFlowSid": "{{flow.flow_sid}}",
          "language": "{{widgets.variables.language}}",
          "botSuffix": "pre_survey",
          "triggerType": "withUserMessage",
          "releaseType": "triggerStudioFlow",
          "releaseFlag": "preSurveyComplete",
          "isConversation": {{widgets.variables.isConversation}},
          "channelType": "{{widgets.variables.channelType}}"
        }
      

  • Create a new Make HTTP Request widget with the following configuration:
    • Name: chatbotCallbackCleanup2.
    • Method: POST.
    • URL: <hrm base url>/lambda/twilio/account-scoped/{%if trigger.conversation%}{{trigger.conversation.AccountSid}}{%else%}{{trigger.message.AccountSid}}{%endif%}/channelCapture/chatbotCallbackCleanup.
    • Content type: Application/JSON.
    • Request body:

        {
          "channelSid": "{{flow.channel.address}}"
        }
      

  • Connect the newly created widgets replacing the old ones used for the channel capture (remember to keep the safeguard that redirects a chat to Flex if the channel capture and/or cleanup fail).
• Enable enable_lambda_post_survey_processing
  feature flag.

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags added
• Strings are localized
• Tested for chat contacts
• Tested for call contacts

Other Related Issues

None

Verification steps

AFTER YOU MERGE

1. Cut a release tag using the Github workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

[stephenhand]

A nitpick about using the correct identifier types.

Honestly I didn't look in detail at the lex implementation itself, just more at how it's integrated into the lambda, which looks good

[stephenhand]

We should use the correct type

[stephenhand]

Use correct type

[stephenhand]

Just the types niggle, otherwise looks good