fix(meta): unify validation logic for system parameters

[Chiro11]

What's changed and what's your intention?

This PR enhances system parameter validation by introducing checks for initial parameter values at startup.

The validation logic is now shared between parameter initialization and runtime updates, ensuring consistent rule enforcement for all parameters, regardless of their mutability.

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• I have checked the Release Timeline and Currently Supported Versions to determine which release branches I need to cherry-pick this PR into.

Documentation

• My PR needs documentation updates.

Release note

[Copilot]

Pull Request Overview

This PR refactors and centralizes validation for system parameters by renaming existing macros/traits, introducing a new “validate all” macro for initialization, and integrating it into the controller initialization path.

• Renamed impl_default_validation_on_set → impl_default_validation and ValidateOnSet → Validate, and moved immutability checks into set_system_param
• Added impl_validate_all_params macro to validate all parameters (including immutable ones) during initialization
• Integrated validate_init_system_params in SystemParamsController and added a test_init unit test

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/common/src/system_param/mod.rs	Renamed validation macro/trait, updated impl_set_system_param to enforce immutability, added impl_validate_all_params and its tests
src/meta/src/controller/system_param.rs	Imported and invoked validate_init_system_params after missing-param checks in initialization

Comments suppressed due to low confidence (2)

src/common/src/system_param/mod.rs:404

• Add a doc comment explaining when to use validate_init_system_params (e.g., it should be called once on initialization) and how it differs from per‐param validation during updates.

        pub fn validate_init_system_params(params: &PbSystemParams) -> Result<()> {

src/common/src/system_param/mod.rs:536

• The test_init function only covers barrier_interval_ms. Consider adding cases for other parameter types (e.g., strings, booleans) and edge values to ensure comprehensive coverage.

    fn test_init() {

[yezizp2012]

Rest LGTM.

[yezizp2012]

LGTM