Search API does not URL-encode searchText query parameter

Description:

The search API request does not URL-encode user-provided searchText before appending it to query params.

In packages/api/src/EmbeddedChatApi.ts (around line 1124), the URL is built with:
...&searchText=${text}

Since text comes from user input (packages/react/src/views/MessageAggregators/SearchMessages.js, line 15), special characters like &, ?, #, % can break or alter query parsing.

Steps to reproduce:

1. Open chat and use Search Messages.
2. Enter a query containing special characters, e.g. hello&room?x#tag%.
3. Trigger search and inspect request/query behavior.
4. Observe incorrect parsing or unexpected search results.

Expected behavior:

searchText should be safely encoded (via URLSearchParams or encodeURIComponent) so all user input is treated as data, not query syntax.

Actual behavior:

Raw user input is interpolated directly into the URL query string, which can corrupt query parameters and change request interpretation.

Start in packages/api/src/EmbeddedChatApi.ts around line 1124, then trace the searchText value from packages/react/src/views/MessageAggregators/SearchMessages.js line 15. Verify the request with characters such as &, ?, #, and %. Done means user input is encoded as one searchText value and no longer changes query parsing or search results.