feat(object): add Object::to_value()

[rami3l]

No description provided.

[peter-jerry-ye-code-review]

Package name string literal should be consistent with project conventions

Category
Correctness
Code Snippet
package "rami3l/js-ffi/js"
Recommendation
Verify if package names should be quoted. If not, revert to: package rami3l/js-ffi/js
Reasoning
The addition of quotes around the package name seems inconsistent with other files in the project. Need to ensure this follows the language's package declaration syntax requirements.

Missing documentation for new Object::to_value method

Category
Maintainability
Code Snippet
pub fn Object::to_value(self : Object) -> Value { self._ }
Recommendation
Add documentation comment explaining the purpose and behavior of to_value method:

/// Converts an Object instance back to its underlying Value representation
pub fn Object::to_value(self : Object) -> Value { self._ }```
**Reasoning**
All public APIs should be documented to improve code maintainability and usability. The purpose of this conversion method should be clear to users of the library.

</details>
<details>

<summary> Test case uses implicit value conversion that could mask errors </summary>

**Category**
Correctness
**Code Snippet**
let obj = @js.Object::from_value_unchecked(@json.from_json!({ "a": 1, "b": 2, "c": 3 }))
**Recommendation**
Consider using the safe `from_value` method and handle the Optional result explicitly:
```moonbit
let obj = match @js.Object::from_value(@json.from_json!({ "a": 1, "b": 2, "c": 3 })) {
  Some(o) => o,
  None => panic("Invalid object conversion")
}```
**Reasoning**
Using unchecked conversion in tests could hide potential runtime errors. Tests should validate proper error handling unless there's a specific reason to use unsafe operations.

</details>