feat: use Recognizer uischema fields to customize Recognizer instance

[yeze322]

Description

#minor
refs #4135
closes #4433

In JS format, Recognizer's uischema can use the seedNewRecognizer method to customize how to initalize an instance.
However, in pure JSON format, we cannot define a function as the value of seedNewRecognizer.

This PR defines a new property fields in recognizer uischema to provide the ability to define how to initalize a recognizer instance in JSON format.

Definitions
With fields, the type of recognizer uischema is defined as

type RecognizerFieldSets = { fields: { [key: string]: string | number | boolean } };
export type RecognizerOptions = Omit<RecognizerSchema, 'id'> & Partial<RecognizerFieldSets>;

The fields is consumed by resolveSeedNewRecognizer.ts.

Examples
To generate dynamic instances,fields is integrated with bf-lg. It consumes the ShellData as the context.
As an example

"Microsoft.SomeRecognizer": {
  ...,
  fields: {
    projectId: "${projectId}",
    dialogId: "${dialogId}",
    locale: "${locale}",
  }  
}

will generate instances like this

{
  "$kind": "Microsoft.SomeRecognizer",
  "projectId": "MyProject",
  "dialogId": "Dialog1",
  "locale": "en-us"
}

PVA
In PVA scenario, we want the recognizer object contain an id field which equals to '${dialogName}.lu'.
With the fields property, we can define its uischema as below:

"Microsoft.VirtualAgents.Recognizer": {
    "recognizer": {
      "displayName": "Default Recognizer",
      "intentEditor": "LuIntentEditor",
      "default": true,
      "fields": {
        "id": "${dialogId}.lu"
      }
    }
  }

Then the instance of PVA recongizer will become

Task Item

Screenshots

[yeze322]

Due to botbuilder-lg becomes a dependency of @bfc/extension-client, there are warnings when executing the script plugin-host-preload.js

[coveralls]

Coverage increased (+0.03%) to 54.5% when pulling c603081 on yeze322:uischema/recognizer-seed into 5af3f50 on microsoft:main.

[a-b-r-o-w-n]

This is cool. I'd like to see our usage of the expression evaluation expanded.

[cwhitten]

@yeze322 conflicts

[yeze322]

blocked by CI process, out of memory error

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

as a low priority feature, target it to R13