Improve Form

[tanbowensg]

What problem does this feature solve?
Before solving this issue, we should design the new spec of the property. #251
related issue: #211

The new Form should improve these points:

• Better array and object editor. Array editor should support different types of item.
• The special forms like FetchTraitForm, EventHanlderForm should use the same form widgets as other normal forms.
• The Form widgets can collapse.
• The Form widgets can be grouped and ordered.
• The Form widgets can display title, description...
• After clicking validation error message, the form auto scroll to the related input. #250 Can auto-scroll to an input.
• Conditional Form. Mainly used in table column form.
• Prevent recursively render form fields for some property, like data in table. Set max height for expression editor.
• Press tab to switch input.
• Value type may change after switch to or from ExpressionEditor.

What does the proposed API look like?

[Yuyz0112]

Better array and object editor. Array editor should support different types of elements(string, object, any...)

What's the expectation of this improvement?

Currently, the ArrayField consists of some array-related operation UI and bypass nested schema to a SchemaField, which will recursively render form fields by the schema.

[tanbowensg]

Can we support conditional form? For example in table column form, a column has many types and each type has its own property. Can we show different fields according to the value of type?

[MrWindlike]

The special forms like FetchTraitForm, EventHanlderForm should use the same form widgets as other normal forms.

@tanbowensg Can the PR's changes meet this point? If yes, I mark it to complete.

[tanbowensg]

The remaining issues has other individual issues, so I close this issue.