feat: iOS TLS fix — defer startTLS until didConnectToHost

[manoaxcend]

No description provided.

[manoaxcend]

@Rapsssito , This PR fixes an issue where startTLS: is not called if the connection is established asynchronously in iOS, leading to silent TLS handshake failures.
Request to review & merge the changes.

Problem
In some edge cases—especially with secure connections and client authentication enabled—the call to startTLS: is skipped when the socket connects asynchronously. This results in:

1. TLS never being initiated.
2. onConnect being called prematurely.
3. Silent failure to negotiate a secure connection.

Fix
This PR introduces two changes:

1. Store TLS Options:
   Save the TLS options in a _tlsOptionsPending dictionary inside connect:.

2. Invoke startTLS on Connect Completion:
   In socket:didConnectToHost:port:, check if _tlsOptionsPending is set and, if so, call startTLS: there. This ensures TLS is always started after a successful connection.

Tested On

• iOS 15–17
• [email protected]+
• Mutual TLS with PEM-encoded RSA 2048-bit certs
• Both immediate and delayed socket connection cases