feat: Schema-driven visual editor - migrates 15 simple types

[yeze322]

UI schema Implementation Plan

• stage 1 (current) - support basic rendering with uischema definition
  • set up uischema definition & implement a generic renderer based on uischema
  • covered $types: 15 simple $types, such as LogAction
• stage 2 - support complicated content rendering
  • extract more widget to support complicated node content
  • covered $types: SendActivity, ReplaceDialog, BeginDialog
• stage 3 - support multiple nodes rendering
  • implement a InputWidget which looks like current BaseInput
  • covered $types: all input $types, such as TextInput, NumberInput (but exclude OauthInput)
• stage 4 - support nested uischema definition
  • extend 'uischema''s definition to support rendering nested $types such as IfConditon, Foreach
  • covered $types: branching - IfCondtion, SwitchConditon; loop - Foreach, ForeachPage;

Description

fixes #1770

Use an uischema definition to define visual nodes' rendering process.
Schema is defined like this:

[SDKTypes.EditArray]: {
    'ui:widget': ActionCard,
    title: generateSDKTitle(),
    content: data => `${data.changeType} {${data.itemsProperty || '?'}}`,
},

[SDKTypes.EndTurn]: {
    'ui:widget': ActionCard,
    title: 'End Dialog Turn',
    content: 'Wait for another message',
}

This pr retires DefaultRenderer and migrates 15 Adaptive types to the new uischema renderer:

• 1. EditArray
• 2. InitProperty
• 3. SetProperty
• 4. SetProperties
• 5. DeleteProperty
• 6. EndDialog
• 7. CancelAllDialogs
• 8. EndTurn
• 9. EmitEvent
• 10. HttpRequest
• 11. TraceActivity
• 12. LogAction
• 13. EditActions (not available in Composer)
• 14. QnAMakerDialog
• 15. OAuthInput

4 $types are influenced by this migration:

• 1. SwitchCondition (add <ConditionNode />)
• 2. IfCondition (add <ConditionNode />)
• 3. Foreach (add <ForeachDetail />)
• 4. ForeachPage (add <ForeachPageDetail />)

To make sure this PR won't bring any different behavior,

• I've checked the render results of all those $types listed above.

Task Item

resolves #1770

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]

I've resolved those formatMessage comments but not very sure about the solution on resolving sdk title, @a-b-r-o-w-n what's your opinion on my comments?

[yeze322]

Made some improvements