Handle macOS EINVAL when enabling TCP_NODELAY on outbound TCP sockets

[Copilot]

The macOS CI job was aborting during the test run because the test host crashed in TcpConnector.OutCompleted while enabling NoDelay on a socket that had just connected. On macOS, this path can surface as SocketException(SocketError.InvalidArgument) rather than the ArgumentException the code already tolerated.

• Root cause

  • TcpConnector.OutCompleted already treated NoDelay setup as best-effort on macOS, but only for ArgumentException.
  • Recent macOS runners are throwing SocketException with InvalidArgument for the same transient condition.

• Change

  • Extend the existing guard around m_s.NoDelay = true to also ignore:
    • SocketException when SocketErrorCode == SocketError.InvalidArgument
  • Keep behavior unchanged for all other socket failures.

• Impact

  • Prevents the macOS test host from crashing during async outbound TCP connect completion.
  • Preserves the existing intent: treat TCP_NODELAY as opportunistic during this narrow connection window.

try
{
    m_s.NoDelay = true;
}
catch (ArgumentException)
{
    // OSX sometime fail while the socket is still connecting
}
catch (SocketException ex) when (ex.SocketErrorCode == SocketError.InvalidArgument)
{
    // macOS may report EINVAL here while the socket is still connecting.
}