feat: Trigger Node

[yeze322]

Description

Task Item

closes #1437

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code refactor (non-breaking change which improve code quality, clean up, add tests, etc)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Doc update (document update)

Checklist

• I have added tests that prove my fix is effective or that my feature works
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have functionally tested my change

Screenshots

Please include screenshots or gifs if your PR include UX changes.

[yeze322]

We need to finalize what's the exact content (grey text) shown in trigger text of each trigger type

Collected some details from design:

Trigger Type	Name to show (black)	Label to show (grey)
Intent	$designer.name > ?	(Intent trigger)
Unrecognized intent	$designer.name > ?	(Unrecognized intent trigger)
Dialog trigger	$designer.name > ?	?
Activity trigger	$designer.name > ?	?
Message activity trigger	$designer.name > ?	?
Custom trigger	$designer.name > ?	?

[mareekuh]

Please show the sub-trigger type name vs the overarching trigger : this is not only more informative, it also removed the repeat of the word 'trigger'.
So for user input this would be Intent or 'not recognized intent'
And for Dialog Triggers

• Dialog started (BeginDialog)
• Dialog cancelled (CancelDialog)
• Error occurred
• Re-prompt for input

For Activity Trigger:

• Conversation started (ConversationUpdate)
• Conversation ended
• Handover to human
• Conversation invoked
• User is typing
• Event received

and for message activity:

• Message received
• Message updated
• Message deleted
• Message reaction (thumbs up/down)

Custom trigger can remain Custom trigger.

[yeze322]

fixed broken test cases

[cwhitten]

@yeze322 we should roll up the form changes into this PR.

[cwhitten]

@yeze322 let's include the form changes in this PR

[github-actions]

Coverage increased (+0.02%) to 39.86% when pulling 91eea69 on zeye/design/trigger into 2f96b52 on master.

[yeze322]

@a-b-r-o-w-n @alanlong9278 could you help rolling up the Form part's changes? I'm not quite familiar with it, thanks!

We need one more subtitle in the form editor which leverages the ConceptLabels map

stale

[yeze322]

Thanks Chris for updating those titles, let me fix CI failures.