chore(message-client): add inbox_id to searchIds (1.30.0)

[dannutiee]

Summary

Regenerate @epilot/message-client from the latest Message API spec to pick up
the new inbox_id parameter on the searchIds operation
(POST /v1/message/threads:searchIds).

Bumps @epilot/message-client 1.29.0 → 1.30.0 (minor).

Why

The central-inbox "Select all" action calls searchIds to get the full set of
matching thread ids. That endpoint was only scoped by the Lucene query, not by
inbox — so "Select all" selected threads across every accessible inbox instead
of just the current one (STABLE360-12157 / SIG-814).

The Message API backend now accepts inbox_id on searchIds and scopes the
result set accordingly. This PR brings that field into the generated client
types so consumers can pass it without a local type cast.

Changes

• src/openapi.json + src/openapi.d.ts: regenerated from prod spec — adds
  inbox_id?: string | string[] to SearchIDParams
• package.json: 1.29.0 → 1.30.0
• CHANGELOG.md: 1.30.0 entry

Related

• Backend: svc-centralized-message-api MR !384 (adds inbox_id to searchIds)
• Consumer: epilot360-messaging MR !1169 (passes inbox_id, will drop its local cast once this is published)

Test plan

• npm run openapi && npm run typegen && npm run build regenerates cleanly
• SearchIDParams now includes inbox_id
• Publish @epilot/message-client@1.30.0, bump + remove cast in epilot360-messaging