Add error handling in InspectorPackagerConnection::connect()

[shubhamksavita]

Summary:
Fix a SIGSEGV crash that can occur during WebSocket connection in the React Native JS inspector when JCxxInspectorPackagerConnectionDelegateImpl::connectWebSocket() fails (for example, due to allocation failure when constructing the WebSocket delegate hybrid object, or a JNI exception thrown from the Java side).

Previously InspectorPackagerConnection::Impl::connect() had no error handling around the connectWebSocket call — any exception (std::bad_alloc, JniException, etc.) would propagate unhandled and terminate the process.

Changes

1. InspectorPackagerConnection.cpp: Wrap connectWebSocket in try-catch. On failure, log the error, reset the WebSocket, and trigger reconnect() (existing 2-second retry mechanism). This is consistent with how other error paths in the same class already handle failures (e.g., didFailWithError and didClose both call reconnect()).
2. JCxxInspectorPackagerConnectionDelegateImpl.cpp: Add a null check on the JNI return value before calling wrapInUniquePtr() to prevent a null dereference if the Java method returns null.

Changelog:
[General][Fixed] - Handle exceptions thrown during WebSocket connect in InspectorPackagerConnection to avoid native crashes when the JS inspector fails to connect
[Android][Fixed] - Add null check on JNI return value in JCxxInspectorPackagerConnectionDelegateImpl::connectWebSocket to prevent null dereference

Differential Revision: D100956267

[meta-codesync]

@shubhamksavita has exported this pull request. If you are a Meta employee, you can view the originating Diff in D100956267.