chore: add description field to FieldFormDialog

[shaohuzhang1]

chore: add description field to FieldFormDialog --story=1019827 --user=刘瑞斌 工具- 使用参数同启用参数一样增加 提示信息字段，目前参数没有说明，不方便使用 https://www.tapd.cn/62980211/s/1782428

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[shaohuzhang1]

The provided code has no major irregularities or critical issues. Here are some optimization and suggestions:

1. Trimming Input: The @blur event on the textarea removes leading and trailing whitespace from the description when it loses focus, improving data integrity.

2. Autosize for Textarea: Enabling autosizing with { minRows: 3 } is a good practice, especially if you expect descriptions to vary in length but should be at least three lines high.

3. Type Definition: It's a good practice to explicitly define the type of form using something like ref<Record<string, string>>, which helps maintain consistency and catch potential errors related to mismatched types.

4. Semi-Colon Usage: JavaScript prefers semicolons at the end of statements except where they're required by syntax (e.g., after commas). While this line does not require a semicolon (`},```), consistency could improve readability.

Overall, these changes make the form more robust and user-friendly, reducing potential edge cases and input errors.