fix: correct TLS type and add missing 'text' search property

[mryraghi]

Summary

This PR fixes two TypeScript definition issues:

1. Wrong TLS type: ImapFlow was importing TlsOptions (server-side) instead of ConnectionOptions (client-side), preventing use of client-specific options like checkServerIdentity
2. Missing text search: The text search parameter is documented but missing from SearchObject TypeScript definitions

Problem 1: Wrong TLS Type

ImapFlow is a client that connects to IMAP servers, but it was using TlsOptions which is the server-side interface from Node's tls module.

Current (incorrect):

import { TlsOptions } from 'tls';

export interface ImapFlowOptions {
    tls?: TlsOptions;  // ❌ Server-side, missing client options
}

Impact: Users cannot use essential client TLS options without type errors:

• checkServerIdentity - Custom hostname validation
• servername - SNI (Server Name Indication)
• session - Session resumption
• minDHSize - Minimum DH parameter size

Current workaround needed:

new ImapFlow({
  tls: {
    checkServerIdentity: () => undefined
  } as any  // ❌ Type assertion required
});

Problem 2: Missing text Search

The text search parameter is documented in the ImapFlow search guide but missing from SearchObject:

text - "Any text (searches headers and body)"

Current workaround needed:

await client.search({ text: "query" } as any, { uid: true });

Solution

1. Changed TlsOptions → ConnectionOptions for correct client-side TLS typing
2. Added text?: string to SearchObject interface with proper JSDoc

After This PR

Users can use proper typing without workarounds:

// TLS options work correctly
new ImapFlow({
  tls: {
    checkServerIdentity: () => undefined,  // ✅ No type error
    servername: 'mail.example.com'         // ✅ Works correctly
  }
});

// Text search works correctly
await client.search({ text: "query" }, { uid: true });  // ✅ No type error

Testing

• ✅ Both features already work at runtime (this just fixes the types)
• ✅ TypeScript compiles without errors
• ✅ No breaking changes (purely additive/corrective)
• ✅ Verified against Node.js tls module type definitions

References

• Node.js TLS docs: https://nodejs.org/api/tls.html#tlsconnectoptions-callback
• ImapFlow search guide: https://imapflow.com/docs/guides/searching
• Node.js @types/node definitions confirm ConnectionOptions is client-side

[andris9]

The package-lock changes are unneeded, and these will get overwritten anyway so the changes are irrelevant. Otherwise LGTM

[mryraghi]

You're right, sorry about that, it slipped into my commit! Anyway, thanks for your prompt merge. Switching from node-imap, which is unstable.