fix: set cookie without port in JitsiMeetView to fix #5852

[bezaleelcheung]

Fixes #5852

Problem

When opening a Jitsi meeting in the Rocket.Chat React Native app, users see a green preloader and never actually join the call when using a custom Jitsi server with a non-standard HTTPS port (e.g., 8443 instead of 443).

This regression was introduced by the fix for #2286, specifically in PR #5458, which added cookie support to the JitsiMeetView component.

Root Cause

The code uses the full meeting URL to extract the cookie domain. However, when the Jitsi server is running on a non-default HTTPS port, the extracted domain includes the port (e.g., example.com:8443), which is not a valid domain for setting a cookie. Per the HTTP cookie spec, the domain should not include the port.

As a result, setting the cookie fails silently, and the JitsiMeetView fails to join the meeting.

Fix

This PR ensures that the cookie domain passed to JitsiMeetView never includes a port number, even when the meeting URL uses a custom port.

Testing

Tested with both:

• Standard Jitsi server at https://meet.jit.si (port 443)
• Custom Jitsi server at https://example.com:8443

In both cases, meetings can now be joined successfully.

[CLAassistant]

All committers have signed the CLA.

[bezaleelcheung]

@OtavioStasiak I see the circleCI error log in “BUild IOS Experimental” ：
OpenSSL::PKey::ECError: [!] invalid curve name
Is there anything I can do？