feat(packages): add builder for ng-monitoring

[wuhuizuo]

Signed-off-by: wuhuizuo [email protected]

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.
The pull request adds a builder for ng-monitoring. The changes are made in the packages.yaml.tmpl file. The builder field has been added under the steps section for release and fips.

There are no potential problems in this pull request. However, it would be best if the pull request description provided more information about the changes made.

As for fixing suggestions, if the pull request description can provide more information, it will be easier for other developers to understand the implementation details and make future contributions.

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.
Overall, this pull request adds a builder for ng-monitoring and also simplifies the existing test script by removing unnecessary loops.

There are no major problems with this pull request, but here are some minor suggestions for improvement:

1. The pull request description is too brief. It would be helpful to have more context about why this change is being made.

2. In the packages.yaml.tmpl file, there are inconsistent uses of whitespace. It would be better to have a consistent formatting style throughout the file.

3. The builder field in the packages.yaml.tmpl file is hard-coded with a specific version number. It might be better to use a variable or parameter instead, so that it can be easily updated in the future.

4. It is not clear if the builder image is publicly available. If it is not, then the pull request should include instructions for how to obtain or build the image.

5. In the pull-verify-packages-config.yaml file, the run command for generating package images has been simplified, but it is not clear if this will cause any problems or if any important functionality has been lost. It would be good to have more information about why these changes were made.

To address these suggestions, the pull request author could update the description to provide more context, ensure consistent whitespace formatting, use variables or parameters for the builder field, provide instructions for obtaining the builder image if necessary, and document any changes to the run command.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [wuhuizuo]

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