Add ldap to the web client's protocol list

[nashcontrol]

interactsh-server correlates LDAP search interactions to the payload's correlation id and returns them in the encrypted data array, but the client filters every interaction against protocols, which was hardcoded to dns/http/https/smtp. Those rows were decrypted and then dropped before reaching the table.

Same shape as #237, which added https.

• ldap added to protocols and to defaultFilter (the second is required, since Filter is Record<Protocol, boolean>)
• LDAP interactions come back without a raw-response, so the response pane and the request/response toggle are hidden for them, the way smtp already is

No migration needed for existing sessions: getStoredData merges defaultFilter over the persisted filter, added in #237 for the same reason.

Tested against a self-hosted server:

• one ldapsearch with the payload label in the base DN produces one ldap row, full-id matching the payload
• the TYPE filter toggles it and the choice persists
• with two payloads open and only one probed, the row lands under that payload only
• also correlates over StartTLS, still reported as ldap, so no separate ldaps entry is needed

Two things worth knowing:

• 389 looks filtered on oast.fun, so this only changes anything against a self-hosted server with the LDAP port reachable.
• Only LDAP search correlates to a payload. Bind, compare and modify are stored under the server token and delivered in the poll response's extra field, which this client doesn't read. Adding smb/ftp/responder from Support for LDAP, Wildcard and additional protocol interaction in web client #95 needs that field implemented first, plus a decision about surfacing server-wide data in a per-payload view. Happy to open a separate issue for it.

Refs #95

[vercel]

@nashcontrol is attempting to deploy a commit to the ProjectDiscovery Team on Vercel.

A member of the Team first needs to authorize it.