fix: improve API parameter parsing in Bridge

[MatrixNeoKozak]

Corrected the parsing logic for API parameters in Bridge.handleApiInvocation. Previously, JSON strings passed as parameters were treated as raw strings, failing API calls that expected structured JSONObject or JSONArray parameters. Updated to attempt parsing string parameters into structured JSON before invoking the API.

[dos1in]

Thank you for your pr, the new global parsing treats any string shaped like {...} or [...] as structured JSON instead of preserving it under args. Existing APIs intentionally pass bare strings through this bridge: canIUse(schema), FileSystemManager.accessSync(path), readdirSync(dirPath), unlinkSync(filePath), etc., and Android handlers read those from args. A valid string value like a JSON-looking filename/path or schema would now arrive without args and fail as “missing file path” or false. Keep direct string params as args, and only parse JSON strings in a narrower API-specific path if that contract really requires it.

[MatrixNeoKozak]

Good point — you're right that treating any {...} or [...] shaped string as JSON at the global level would silently break APIs like canIUse(schema) or accessSync(path) that intentionally pass bare strings through args. The intended fix was narrower than what I ended up implementing. If there's a specific API contract in the bridge that expects a pre-parsed object rather than a raw string, the safer approach would be to handle that on the handler side rather than at the invocation level. Happy to close this if it's not something you're planning to address at the bridge layer — just let me know.