internal: support --enable-value-tracing for build-package

[Young-Flash]

No description provided.

[peter-jerry-ye-code-review]

‼️ This code review is generated by a bot. Please verify the content before trusting it.

Here are three observations from the git diff output:

1. Missing Default Value for enable_value_tracing in scan_one_package:

   • In crates/moonutil/src/scan.rs, the enable_value_tracing field in the Package struct is initialized to false in the scan_one_package function. However, this field is not set in the Package struct initialization in other parts of the code (e.g., crates/moonutil/src/package.rs). This inconsistency could lead to unexpected behavior if the field is accessed before being explicitly set.

2. Potential Missing Documentation for enable_value_tracing:

   • The enable_value_tracing flag is added as a hidden CLI option (#[clap(long, hide = true)]). While this might be intentional for internal use, it would be beneficial to document its purpose and usage in the code or in a separate documentation file to ensure clarity for future developers.

3. Inconsistent String Formatting in Test Output:

   • In crates/moon/tests/test_cases/mod.rs, the test output for test_tracing_value uses a mix of raw string literals (r#""#) and multi-line raw string literals (r#######""#######). This inconsistency in formatting could make the test output harder to read and maintain. It would be better to standardize the formatting for consistency.

These observations highlight areas where improvements can be made to ensure code consistency, clarity, and maintainability.