Introduce Interaction support to Slacker

[SapphicFire]

Description

#360 introduced a Quiz parser which incorporated interactivity. Before that, #369 and #387 implemented buttons which by default trigger interactivity. Additionally, existing functionality for a code-snippets related interaction and slash command was introduced, which currently leverages the interactivity URL and throws messages in a specific channel when buttons are used, as per #429.

This PR introduces support for Interactivity in the app as a first-class object alongside parsers. This implements:

• A new scripted REST API
• A new table for Interactions
• A new field on Payload to distinguish payload type
• Updates to the SlackerBot Event Handler REST API to remove fragile quiz handler functionality
• Updates to the SlackerBot GitHub REST API to handle Interactions as well as parsers
• Updates to business rules on Payload to only run on their appropriate payload type
• An update to the Parse chat business rule to run async to address scoped synchronous REST error
• First interaction handler for Quiz
• Various form, list, and acl changes as required.

Resolves #429

Usage

Interaction is designed to be used with interactive Slack block components. In particular, this implementation looks for a regex match within the action_id that the user interacts with. The first example of this is the Quiz Parser, which sets a standard prefix for its action_id. The Interaction handler includes this prefix and will match these events. Other interactions that don’t match will be disregarded silently, which means no error messages to the user which otherwise occur when the interactivity components is not configured appropriately.

Set up

In order to activate the Interaction functionality, the following steps must occur

On Slack App:

• Update the Interactivity request URL in the live Slacker app config to https://INSTANCE.service-now.com/api/x_snc_slackerbot/slackerbot_event_handler/interaction

On DPR:

• Retrieve remote app

On GitHub:

• Re-run the Workflow for syncing the parsers and interactions with DPR from pushing this PR. This will let the app pull down the first Interaction handler. Otherwise create by hand or nudge the name

Remaining activities to do (will document as issues):

• Document how to set up Interactions as per parsers
• Add a Sync Interaction list UI action as per Sync Parser
• Update manifest file to incorporate new URL

[earlduque]

Github side of things looks fine. i rather just push the xml side live and see what happens!

[earlduque]

all testing went well. old parsers working, new quiz parser working.

great work astrid!