feat: support get cli args & env var

[Young-Flash]

No description provided.

[peter-jerry-ye-code-review]

From the provided git diff output, I've identified several issues that could potentially lead to bugs, typos, or inconsistencies in the MoonBit codebase. Here are the top three problems I've observed:

1. Misuse of String Substring Method:

   • In multiple files (e.g., json5/lex_number.mbt, json5/util.mbt), the substring method is called with potentially incorrect arguments due to the use of the ~ operator for optional parameters. This operator should not be used in this context.
   • Problem: The ~ operator is used for optional parameters, but it seems incorrectly applied here, leading to potential issues with string manipulation.
   • Suggestion: Remove the ~ operator from the substring method calls to correctly pass the start and end indices.

2. Incorrect Use of Optional Parameters in Function Calls:

   • In several files (e.g., time/duration.mbt, time/period.mbt), functions are called with optional parameters using the ~ operator, which is not standard for calling functions in MoonBit.
   • Problem: The ~ operator is used for optional parameters in function definitions, but it should not be used when calling those functions.
   • Suggestion: Remove the ~ operator from the function calls to correctly pass the optional parameters.

3. Potential Logic Error in UUID String Conversion:

   • In uuid/uuid.mbt, the to_string function uses rv.to_string() which might be incorrect if rv is already a string buffer.
   • Problem: The to_string method is called on an array of bytes (rv), which might lead to incorrect string conversion.
   • Suggestion: Use rv.to_unchecked_string() instead of rv.to_string() to directly convert the byte array to a string without additional processing, assuming to_unchecked_string is the correct method for this context.

These issues, if not addressed, could lead to runtime errors, incorrect string manipulations, or unexpected behavior in the code. Addressing these suggestions will help ensure the code is more robust and follows the correct conventions for MoonBit.

[Young-Flash]

this requires moonbitlang/moon#470, ci would pass after next stable release

[peter-jerry-ye]

LGTM

[mengzhuo]

Related #71