fix: remove accidentally leaked apis

[peter-jerry-ye]

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 provided git diff output:

1. Potential Issue with moon check Command:

   • The moon check command has been updated to include the --target all flag. This change might affect the scope of the checks being performed. Ensure that this flag is intended and that it aligns with the project's testing strategy. If --target all is not necessary, it could lead to unnecessary overhead or unintended behavior.

2. Visibility Changes in Type Definitions:

   • Several types (JSArray, JSValue, Int64WasmHelper) have been changed from public to private (priv). This could potentially break existing code that relies on these types being publicly accessible. Review the usage of these types across the codebase to ensure that this change does not introduce compilation errors or runtime issues.

3. Addition of diff Command in moon info Step:

   • A new diff command has been added to compare the output of mooninfo for two different targets (js and wasm-gc). This addition is useful for ensuring consistency between different build targets. However, ensure that the paths (target/js/release/check/builtin/builtin.mi and target/wasm-gc/release/check/builtin/builtin.mi) are correct and that the files exist at these locations. If the paths are incorrect, this command will fail.

These changes seem to be focused on improving the robustness and maintainability of the code, but they should be carefully reviewed to avoid introducing new issues.

[coveralls]

Pull Request Test Coverage Report for Build 4564

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 83.295%

---

Totals
Change from base Build 4551:	0.0%
Covered Lines:	4727
Relevant Lines:	5675

---

💛 - Coveralls

[hackwaly]

UInt64 is not safe to represent in Double. I think UInt64::to_double is not a good name?

[peter-jerry-ye]

It is as good / bad as (int)1.0.

[bobzhang]

We should not do two things in a single PR, can you split your changes (as tilte) into a single PR?