[Task] Feature Request: Form Configuration for Reusable Monitoring Template Parameters

### Description

**Description**:
- In HertzBeat, each monitoring template requires the user to input various parameters, some of which may be common across multiple templates. Currently, users must manually enter these parameters for each template, which can be time-consuming and error-prone.

**Proposed Feature**:
- Implement a feature that allows users to create reusable form configurations for commonly used parameters. This would enable users to save a set of parameters as a configuration and then select the appropriate configuration when creating new templates, reducing the need to re-enter the same information.

**Use Case**:
- A user who needs to set up multiple monitoring templates for different services might have to input the same set of parameters (e.g., Prometheus HTTP API parameters, database connection strings, etc.) for each template. With the proposed feature, users could save these parameters as a configuration and then simply select the configuration when creating a new template, making the process more efficient and less error-prone.

**Benefits**:
- This feature would save time for users by reducing the amount of manual input required.
- It would also help maintain consistency across templates and minimize the chance of input errors.

### Task List

_No response_

The issue does not name files, tests, or entry points. Start by tracing how monitoring template parameters are defined, entered, stored, and applied, including the Prometheus and database examples. Done should include an agreed configuration model, its selection when creating templates, and coverage for saving and reusing configurations.

Written by the indexing model from the issue text.